On 25/10/13 20:21, Olemis Lang wrote:
On Thu, Oct 24, 2013 at 9:28 PM, Branko Čibej <[email protected]> wrote:
On 24.10.2013 17:35, Joachim Dreimann wrote:
On 23 October 2013 20:31, Olemis Lang <[email protected]> wrote:
On Tue, Oct 22, 2013 at 11:24 AM, Branko Čibej <[email protected]>
wrote:
On 21.10.2013 19:12, Joachim Dreimann wrote:
On 19 October 2013 14:07, Branko Čibej <[email protected]> wrote:
>
[...]
>>> I would suggest adding a kind of visual hint that the links are there
in
the create-ticket dialogue; it seems a bit counter-intuitive to me to
click "Create Ticket" in order to see which tickets I've recently
created.
I agree . In spite of comparing vs an alternative , what about something
like this ?
https://redpen.io/qp8yvj
--
Regards,
Olemis - @olemislc
I guess this could work, but please also consider where/how it will be
displayed on mobile devices for example.
I added some commentas about it bur redpen never saved those , no matter
how hard I tried ...
I see that on mobile devices, the Create Ticket drop-down is condensed
to just an icon. The same could be done in this case (there's enough
room for it on my phone even when I hold it in portrait mode).
... and I was trying to say something like this ...
So ... add a a "Recent" drop-down, and invent an appropriate icon for
mobile layout.
ok
Regarding behaviour, I propose:
* "Recent" items should have a timeout. How long is debatable, but I'd
say that they should be cleared, and the button removed, when the
current session expires (e.g., the user logs out).
* There should probably be a limit on the number of recent items
displayed, with only the N "most recently used" items showing up
* "Recently used" gets bumped to "now" if the user navigates to one of
the items, whether via the "recent" dropdown, or by some other means
* I can't think of a good reason to limit "recent" only to tickets --
other than that we currently only have a quick-create-ticket mode.
Perhaps, if BH ever gets another quick-create-whatever, that
whatever should also be added to the recent items.
Last but not least: perhaps recent items should have a component
interface, so that BH-specific plugins can manage them?
I see the workings of a whole new BEP here ...
Ok , initially in #696 I'll submit a patch for a subset of all this . There
will be another ticket for the rest . I'm doing this in spite of
prioritizing other pending (major) issues
Sorry I have been so quiet on this and only start making suggestions now.
When considering the original problem, I do prefer Joe's solution as it
feels like there is little reason for this being a semi-permanent
control which is part of the main display, particularly as I am not
convinced that it would be enough use to enough people. This is partly
as I suspect that for most users so much information about previously
raised tickets is generally only required when the user is creating lots
of tickets. Under those circumstances we should probably be providing
something like a tabular interface for raising multiple tickets to keep
the information in view.
The quick ticket form is really a bit better for quickly raising a
ticket while you happen to have it in mind - you either don't really
need to know what the ticket is until way later or you will probably
just open the created ticket in a new tab.
The other advantage that Joe's suggestion has is that it should also be
a fair bit simpler to implement and it only dealing with the specific
problem originally raised.
However, I was thinking that something like the suggested control might
be useful if it is combined with additional features. A short list of
recently created and recently visited tickets is all very well but if
you also had a partial list of the tickets from the current ticket
query, that would seem to be useful for a wider range of people.
Effectively I am hoping for something that is an effective replacement
for the previous ticket, next ticket and back to query links.
Does this strike anyone else as worth considering?
Cheers,
Gary
