some feedback after switching this on for a short while (switched it back off now)
Links - when there are no links on a ticket, the option to add new is a bit hidden. Users linking tickets is often a battle to encourage. Adding links needs to be more prominent
The section titles (description etc) are a bit grey. Need to be bolder otherwise they just blend in with the rest of the text on the ticket so hard to distinguish between the sections (they seem to be bolder in the screenshots on this article - less so in my instance)
FixVersions, two issues noted
Create new fix version from the ticket doesn't seem to work
Clicking on an existing fixversion now takes you to a search of the fixversion rather than the release page.
I do much prefer the history though, especially the mark up on what has changed in a text field. Also the prominent status colour and fixing the ticket summary to the top when scrolling is much better. Finally i do like how fields not filled in do not take up as much space as before.
In JSM -> Agent view -> Attachments used to show a lock when they are not shared with customers, this is gone now, and we are getting lots of complaints from our Agents.
Any plans to differentiate between Internal attachments and Customer shared attachments?
Amazed that no-one else has yet raised the absolutely awful change to give no visual indication that there are more sub-tasks than currently shown other than an easily missed, small and somewhat feint "Show All" link at the bottom of the list.
We've had multiple people not realise that there are more subtasks than are shown and think they're done on the main task once they've completed 5 (? or is it 6?) sub-tasks that are shown.
Stunned that this made it through any form of UI/UX testing as it's truly attrocious!
> Amazed that no-one else has yet raised the absolutely awful change to give no visual indication that [...]
I think, that's because not many people have yet seen it (I guess the ones here that have a sandbox available). In my case I have to rely on the screenshots and descriptions.
> We've had multiple people not realise that there are more subtasks than are shown and think they're done on the main task once they've completed 5 (? or is it 6?) sub-tasks that are shown.
If this is the case, there will be a lot of backlash from a large part of my users. When working in customer projects, we regularily have ~20-30 tasks per Epic (depending on the project, vastly more). I understand the idea though. A long list of subtasks will mess up the overview. A better way - I think - would be to move the subtasks to a different tab ("tab" as in screens use them) but then show them all at once. This way, users can be easily taught to click there and have all in sight at once.
Additional question to those who are already testing:
In Jira, when looking at lists, it shows 50 work items (or something like that) and then has one click "show more" for every 50 work items one wants to see more. Is there something like that as well in the list of subtasks shown in the "subtask" section (progressive listing)?
I hadn't used Jira for a while and jumping back in was a piece of cake. Things were clear, intuitive, and easy to find; however, this update has taken the easy to use experience away... Initial thoughts on this update:
There is too much dead space between things = more scrolling, more time
Child work items need to be expanded if there are a few = extra clicks and duplication if you don't know to look/click before creating something
Activity section is too simple by using icons only = it feels harder to interact with. I've had multiple people ask me how to use it and how to add the note! If they are using Grammarly, it covers the small arrow button...
Attachments, child work items and linked work items icons = hovering to see what each of them are adds more time...
Being able to re-order fields is good!
It feels like you have to 'work it out how to use it' now, rather than just using it. We didn't need user training when we released Jira, but I have a feeling we'll need it now - mostly on where to click, what icons mean... Use words and make buttons clear - it is easy. Like a stop sign - if you take away the word STOP, it is open to interpretation; it needs to be clear that it means stop - it shouldn't be a question! If I were new to Jira, this would put me off, and I'd be considering alternatives.
35 comments