Not a fan of the new placement of the "Status" button. If Atlassian insists on keeping it there, then they should at least lock the header where the Summary, Plus Button, Status are. Fix that in place so as we scroll down we can see / edit the status (especially after reading a comment). Or move it back to where it was (which myself and team prefer).
This has now increased effort for everyone when making transitions. They now have to scroll up to the top of the issue in order to make the transition. I don't know why this was changed. It was grouped together with other similar fields.
How is the new location "more visible" when it literally is not visible on the screen at all whatsoever once you scroll down, and beforehand, it was? Do you understand that the change you made, that you are claiming is increasing visibility, literally makes it so the element in question is not on the screen most of the time?
I don't think you thought this through at all and the level of obviousness of the negative impact of this change makes me doubt the effectiveness of your UAT process.
Here's a free UX tip for you guys: make the issue name, status, and related work button sticky just like the breadcrumb trail.
- You have a long ticket description, status is lost.
- You have a long testing comment, status is lost
- You're donkey deep in "replies" [another bug bear], status is lost.
Grouping it together with the rest of the ticket info was perfect - either that or make the header information sticky. This is ridiculous, I would love to see the results of the A/B test.
255 comments