On 17/12/13 14:22, Olemis Lang wrote:
Hi !
Recently I have received user feedback from Bloodhound users and wanted to
highlight these points for us to discuss (as usual, my comments inline) :
- After ticket creation, if the ticket is automatically assigned
(depending on the product), the ticket status is inconsistent. When
you enter the ticket url, you can see that the ticket has been
assigned to xxxx, but the ticket status is still new. You must
manually modify the ticket status and select "reassign to: xxxx" so
that the ticket status becomes "assigned".
If the ticket is automatically assigned on creation, the ticket status
must be changed accordingly without user intervention.
That is interesting. So automatic assignment is controlled by the
[ticket] default_owner setting. Given that this is not guaranteed to be
a real user, the automatic change in status may not be considered
appropriate by some.
It might be interesting if we could introduce the ability to distinguish
real from fake users in a transition and I think this could do with
thinking through further. I find myself worrying about changing this as
a default behaviour as some may rely on the old behaviour.
- <note>using quick create ticket shortcut</note> Besides the automatic
assignment function... It would be good to be
able to assign the ticket to any user (working in the project) from
the creation window itself.
For example: The case when you have 3 people working on the same
product and you want to assign the ticket to any one of them. Right
now, the automatic assignment would always assign the ticket to the
same owner and then the user would have to manually change the owner
to the desired person.
I think we would also have to get assignment as something you could do
in the newticket interface to help support this. Otherwise I think that
could be good.
I sometimes wonder if it is worth providing any support for assigning to
a group to allow people to reduce emphasis on a single owner of an
entity for teams where that is less appropriate.
A final note on this is that the QCT creation appears to avoid the
automatic assignment.
- When writing a user name to assign a ticket (or whatever)... Like in
Modify Ticket --> Reassign To. It would be good to have some help like
a user list displayed as we type.
There is a ticket for this - https://issues.apache.org/bloodhound/ticket/185
Currently there is no help, so I
must know the user name and type it (hopefully) without errors.
A dynamic list that displays the user names as we type and allows to
select a user name from the list (actually this should probably be a
constraint) would improve the usability and prevent typing errors and
assigning the ticket to the wrong owner.
Also this list should be filtered so only the users working in the
product would show
Yes, the latter point could be important though it effectively requires
a pre-selection of the product. Not the end of the world of course.
<note>
we have developed a plugin for the feature above , see
https://github.com/olemis/trac-mentions
</note>
- There is no easy way to see the tickets that I create as a reporter.
They do not show in the dashboard. The feature of showing only the
last created ticket in the creation window is a bit obscure (I need to
click "Create Ticket" to find out which is the last created ticket)
not to mention lacking because if I had created 5 tickets, only the
url of the last one would show here. For the other ones, there is no
easy way to access their url.
Ideally for me the tickets that I report, would show in my dashboard.
This way I could easily see the list by clicking "Dashboard'. Right
now the alternative is to use a report (not always can find the right
one). In practice I end-up creating a custom query just to see the
newly created tickets, which is a tedious task (click Custom query,
configure it, add/remove query parameters, select Status=new, type my
own name as reporter)
<note>I see this feature deployed at i.a.o/bh/report/7 , maybe we should
just distribute that query in default BH installation ?</note>
I understood the report to be available on all new installs. It could of
course be nice to have a custom query that gives similar results too.
Cheers,
Gary
