Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of joachim.dreimann@wandisco.com
 designates 209.85.215.175 as permitted sender)
Subject: Re: [Apache Bloodhound] #258: Upgrade i.a.o/bh to v0.2
References: <058.688e970b604035ecb3c29c43e8620d08@incubator.apache.org>
 <073.3d3a107ab43595971c4d49646c98ce1f@incubator.apache.org>
 <CAKoya91r2fv495EcHxE-ndBPKWW=KFjRCyq+u6FX4yWEFP0hcg@mail.gmail.com>
 <50AB751A.3020106@wandisco.com> <50ACC0CA.3000005@wandisco.com>
From: Joe Dreimann <joachim.dreimann@wandisco.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <50ACC0CA.3000005@wandisco.com>
Message-Id: <DB67D0D1-23F2-4C35-A93D-494B39B5760C@wandisco.com>
Date: Wed, 21 Nov 2012 13:46:55 +0000
To: "bloodhound-dev@incubator.apache.org"
 <bloodhound-dev@incubator.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

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 <gary.martin@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!
>>>=20
>>> 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
>>>=20
>>> Why is that?
>>=20
>> Simple.. we only get open and close events at the moment. This might be f=
ixed by showing more of the events with
>>=20
>>    [timeline]
>>    ticket_show_details  =3D  true
>>    abbreviated_messages  =3D  true
>>=20
>> We will still be left with a limit on the time period though. Still we ca=
n experiment with the site configuration to see if we do want to implement #=
69 or improve further.
>=20
> There appear to be a few things that need improving on the activity feeds:=

>=20
> * 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.
>=20
> #69 doesn't appear to cover the last point as I think the abbreviated_mess=
ages setting is ignored by the activity area.
>=20
> Cheers,
>    Gary