> On 17 Oct 2013, at 23:14, Olemis Lang <[email protected]> wrote: > > I'm forwarding this message on behalf of a user (after translating the > original text in Spanish, adding a bit of slang-ish terms and > inserting my own comments ;) . I mostly agree in some points that's > why I'm forwarding it to the ML, especially to request for keeping QCT > ticket notification visible long after creation, figure out how/where > to include it and file a new ticket @ i.a.o/bh . > > <msg> > > When QCT form is submitted there's no confirmation indicating that > ticket was actually created except for the small window that pops up > after a while (<= due to limited bandwith it takes a while to be > shown) and that , at least in my case , captures whole attention > because > > 1. it remains open for about 2 or 3 seconds > 2. if using a laptop mouse pad then it ends up to be extremely > complicated to follow ticket link (<= obviously not a Mac user) > 3. if the popup is missed for any reason then finding the ticket > is a time consuming task, at least more time-consuming than > it should be due to the fact that: > * ticket URL has to be guessed > * ticket does not show up in dashboard (<= owner and component > not in QCT) > * therefore a custom query is required > 4. the default configuration is sub-optimal since it's always necessary to > surf to ticket page in order to fill remaining fields > (<= component , priority , custom fields , ... which otoh are > configurable). > > 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. > > </msg> >
These tickets should be easy to find by the Reporter field using Custom Query and sorting by descending ticket ID. The first ticket is the one last raised by that user. That's the best way to keep track of tickets raised throughout the day too. I understand the concern about the notification box disappearing too quickly, but I'm sceptical of just having it stick around for (much) longer. If there is demand for such a solution, how about we instead append a simple informational one liner providing the ticket ID you last created to the QCT box? See my mockup here: http://redpen.io/tfox7u - Joe > -- > Regards, > > Olemis - @olemislc
