Jira - how to move the ticket status to the right side panel

[Manish Keswani]

I don't know who your UX designer is, but you should fire them immediately. Moving the ticket status to the main window is a bad decision. The status move our of view when we scroll down. We can't change the status without having to scroll back up. You broke something that was working perfectly. I hope you have a setting to restore the position of the ticket status back to the right side panel.

[Valerie Knapp]

Hi @Manish Keswani , thanks for your post.

For the moment, Atlassian are saying they will not roll back this change - https://community.atlassian.com/forums/Jira-articles/Easier-status-updates-for-work-items/ba-p/3068881 

There is a suggestion you can vote on to be allowed to move the Status to where you want it - https://jira.atlassian.com/browse/JSWCLOUD-27789 

or some people have started posting their workarounds in the comments of the original article.

Best wishes

[Nikola Perisic]

Hello @Manish Keswani 

Your frustration is understandable. However, this forum is here to answer to the questions and solve the issues that the users have. Trust me, you are not the only one who is having an issue with this. I'd suggest you speak to Atlassian directly by sending a support ticket and ask why is it like that. Other than that, there is nothing much that can be done here.

[Tomislav Tobijas]

Hah, I can just say that I understand the pain here... @Manish Keswani 😩 I'm just glad that our main instances are on release tracks and change still hasn't rolled out there...yet. But once it does, it will probably cause a lot of headaches.

My best bet is that they won't go back/revert it as it's the middle of the rollout, but based on the feedback on the link Valerie posted, it might go in the direction where users can switch layouts and set their own preference, where you could switch between the new status location or the 'previous' one. At least that's what I hope will be the case 🤞

[Olivier Ruis]

Not to mention that such unexpected changes require updating the custom end-user manuals that we have written... It constantly happens since few months...