We noticed this morning that the the Status dropdown moved from the upper right part of static menu to the top of each ticket. We have tickets that have lengthy descriptions and each time we add a comment and change a ticket status, now we're forced to scroll up through the description to get to the Status dropdown.
It's a really bad user experience.
Voicing my complaint with this UX change too. Like others, I find I am scrolling a lot more now. It was great where it was previously as it was part of a workflow. Now I have to not only have scroll up and down, I also have to move my mouse horizontally more.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry but this is just a bad UI decision. What should be done is to have this configurable to fulfill either user requirement. I can't work our why anyone would want it where it is now, but I'm not everyone, for our users as as soon as you scroll to look at comments etc. you then have to scroll back up to change the status!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It has Vertical Scroll for both Description/Comment and Status Section.
So, updating Description or Comment has no impact on the right side navigation Pane as it has separate Vertical Scroll.
Thank you,
Ashish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, true but we didn't need to scroll at all with the fixed location at the top of the right column. (And we set up our view such that we don't need to scroll the right column very often).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok. This change needs to be reverted. Do you people actually use your product? Who in their right mind thought this was a good idea? I am FURIOUS - this has totally disrupted my team and workflow. It is insane this got out to production.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Heres a Tapermonkey script to move the button back into it's correct place: https://gist.github.com/tsurna/0640a2e88f3e537de8c3a021be4b40b6
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Janelle Schultz , welcome to the Atlassian Community!
This change was announced in July of this year, and has been detailed as part of this Community Article: https://community.atlassian.com/forums/Jira-articles/Easier-status-updates-for-work-items/ba-p/3068881
Atlassian has an open request in their feedback portal to provide organizations the option to move the Status field where the want, which I would recommend you voice your support for here: https://jira.atlassian.com/browse/JSWCLOUD-27789
Cheers,
Robert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you - I disagree with the reasoning behind this change and I will voice my support for the customization. Given how long it takes for Atlassian to make changes based on community feedback, I'll just assume we are going to be doing an inordinate amount of scrolling.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't have time to monitor the development of JIRA. I have work to do. It is insane to make a huge change like this - the status is a key item.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I also disagree with this change and have a number of very angry users today. I also voice my support for the customization - either that, or revert this change. This is a major disruption in using Jira for all my users and will result in frustration and wasted time, as well as a bad reputation for Atlassian. Atlassian should listen more carefully to their customers who reported the issue during beta and early releases. And the sooner the customization is put in place, the better. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Janelle Schultz -- Welcome to the Atlassian Community!
This is one of the recent UX updates, and there are already customer suggestions to reverse the decision or to make the Status control position configurable.
Here is one of those suggestions, which you may watch / vote for to see progress:
https://jira.atlassian.com/browse/JSWCLOUD-27789
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A jarring and unexpected change!!! I just got comfortable with status on the right pane - it moved from the left to the right pane only a few years ago. Now it's moved back? Why o why do you do this to me Atlassian?!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It WAS jarring and I have had users not updating the status (which is part of our routing process). At least the right pane is static whereas the location now means far more scrolling just to advance a ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I see how status is hard to find on a narrow display, like mobile. The stuff on right pane is moved below the stuff on the left pane.
But improving mobile shouldn't mean messing up the rest of us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.