You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Joachim Dreimann <jo...@wandisco.com> on 2012/11/20 12:46:39 UTC
Re: [Apache Bloodhound] #258: Upgrade i.a.o/bh to v0.2
Thanks for the update Gary - our own Bloodhound instance is now upgraded to
0.2, yay!
Olemis has highlighted an issue with the activity feed though, often no
events are shown, like on this ticket:
https://issues.apache.org/bloodhound/ticket/240
Why is that?
Cheers,
Joe
On 19 November 2012 18:51, Apache Bloodhound <
bloodhound-dev@incubator.apache.org> wrote:
> #258: Upgrade i.a.o/bh to v0.2
> ------------------------+--------------------
> Reporter: jdreimann | Owner: gjm
> Type: task | Status: closed
> Priority: major | Milestone:
> Component: siteadmin | Version:
> Resolution: fixed | Keywords:
> ------------------------+--------------------
>
> Comment (by olemis):
>
> IMO , something needs to be enhanced. For instance, last comment for #195
> happened 10 days ago . Nonetheless Activity feed is empty . That gadget to
> the right is not really useful in ticket view unless ticket details are
> contributed to the timeline ( #69 ? ).
>
> --
> Ticket URL: <https://issues.apache.org/bloodhound/ticket/258#comment:4>
> Apache Bloodhound <https://issues.apache.org/bloodhound/>
> The Apache Bloodhound (incubating) issue tracker
>
--
Joe Dreimann
UX Designer | WANdisco <http://www.wandisco.com/>
*
*
*Transform your software development department. Register for a free SVN
HealthCheck <http://go.wandisco.com/HealthCheck-Sig.html> *
Re: [Apache Bloodhound] #258: Upgrade i.a.o/bh to v0.2
Posted by Joe Dreimann <jo...@wandisco.com>.
I agree with all of those points. Thanks for raising them Gary.
- Joe
________________________
@jdreimann - Twitter
Sent from my phone
On 21 Nov 2012, at 11:53, Gary Martin <ga...@wandisco.com> wrote:
> On 20/11/12 12:18, Gary Martin wrote:
>> On 20/11/12 11:46, Joachim Dreimann wrote:
>>> Thanks for the update Gary - our own Bloodhound instance is now upgraded to
>>> 0.2, yay!
>>>
>>> Olemis has highlighted an issue with the activity feed though, often no
>>> events are shown, like on this ticket:
>>> https://issues.apache.org/bloodhound/ticket/240
>>>
>>> Why is that?
>>
>> Simple.. we only get open and close events at the moment. This might be fixed by showing more of the events with
>>
>> [timeline]
>> ticket_show_details = true
>> abbreviated_messages = true
>>
>> We will still be left with a limit on the time period though. Still we can experiment with the site configuration to see if we do want to implement #69 or improve further.
>
> There appear to be a few things that need improving on the activity feeds:
>
> * Using N days back as a means to limit the number of events to show
> appears to be flawed
> * The message shown when no events are available is misleading in
> implying that there could be a misconfiguration. If we are going to
> maintain the above time limit, we need to be far more optimistic.
> * All ticket events should be shown (#69)
> * Events that have comments should have those comments abbreviated by
> default. At some point we will probably want to allow the user to
> view more details of an event without having to go to the ticket but
> that seems secondary to the problem of showing more detail than
> required.
>
> #69 doesn't appear to cover the last point as I think the abbreviated_messages setting is ignored by the activity area.
>
> Cheers,
> Gary
Re: [Apache Bloodhound] #258: Upgrade i.a.o/bh to v0.2
Posted by Gary Martin <ga...@wandisco.com>.
On 20/11/12 12:18, Gary Martin wrote:
> On 20/11/12 11:46, Joachim Dreimann wrote:
>> Thanks for the update Gary - our own Bloodhound instance is now upgraded to
>> 0.2, yay!
>>
>> Olemis has highlighted an issue with the activity feed though, often no
>> events are shown, like on this ticket:
>> https://issues.apache.org/bloodhound/ticket/240
>>
>> Why is that?
>
> Simple.. we only get open and close events at the moment. This might
> be fixed by showing more of the events with
>
> [timeline]
> ticket_show_details = true
> abbreviated_messages = true
>
> We will still be left with a limit on the time period though. Still we
> can experiment with the site configuration to see if we do want to
> implement #69 or improve further.
There appear to be a few things that need improving on the activity feeds:
* Using N days back as a means to limit the number of events to show
appears to be flawed
* The message shown when no events are available is misleading in
implying that there could be a misconfiguration. If we are going to
maintain the above time limit, we need to be far more optimistic.
* All ticket events should be shown (#69)
* Events that have comments should have those comments abbreviated by
default. At some point we will probably want to allow the user to
view more details of an event without having to go to the ticket but
that seems secondary to the problem of showing more detail than
required.
#69 doesn't appear to cover the last point as I think the
abbreviated_messages setting is ignored by the activity area.
Cheers,
Gary
Re: [Apache Bloodhound] #258: Upgrade i.a.o/bh to v0.2
Posted by Gary Martin <ga...@wandisco.com>.
On 20/11/12 11:46, Joachim Dreimann wrote:
> Thanks for the update Gary - our own Bloodhound instance is now upgraded to
> 0.2, yay!
>
> Olemis has highlighted an issue with the activity feed though, often no
> events are shown, like on this ticket:
> https://issues.apache.org/bloodhound/ticket/240
>
> Why is that?
Simple.. we only get open and close events at the moment. This might be
fixed by showing more of the events with
[timeline]
ticket_show_details = true
abbreviated_messages = true
We will still be left with a limit on the time period though. Still we
can experiment with the site configuration to see if we do want to
implement #69 or improve further.
Cheers,
Gary