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:
>>> >
>>>
>> [...]
>>
>>>>>>>>> On 17 Oct 2013, at 23:14, Olemis Lang <[email protected]> wrote:
>>>>>>>>>
>> [...]
>>
>>>>>>>>> Summarizing , the confirmation of the most recent ticket must
>> remain
>>>>>>>>> in the page just in case it's not possible to capture QCT
>>> notification
>>>>>>>>> and browsing to ticket page is still needed.
>>>>>>>>>
>>>> Here's my mockup again just for reference:
>>>> http://redpen.io/tfox7u
>>>>
>>>> The user asked for a link to the last created ticket. Why over-engineer
>>> it?
>>>
>>> Ah, this in fact looks pretty good. There could even be several links to
>>> recent issues, instead of just the one (I guess making the notification
>>> area two lines high instead of one isn't that bad).
>>>
>>> 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 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).
So ... add a a "Recent" drop-down, and invent an appropriate icon for
mobile layout.
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 ...
-- Brane
--
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. [email protected]
