Issue Status button relocated bringing poor UX

[Kris]

It seems Atlassian has relocated the Issue Status button from the Context fields to the Description fields.

Is it possible to move it back to the Context fields?

I’ve received numerous complaints from users who are finding it difficult to change the issue status. The button is not clearly distinguishable and blends in with the +Add buttons, particularly when the status is To Do.

I’m unsure how this change enhances the user experience, but it would be much better if Atlassian either made the Title and Issue Status button sticky or reverted the change altogether.

[Shalini Pradhan · Accepted solution]

Hello @Kris,

Good day! :)

The change of the status under the Description field is part of an Atlassian experiment to guide users to the most valuable tasks, such as adding content and progressing status, helping them to focus better on important actions.

Looks like your instance is part of this experiment and that is why you see this change. 

If you would like to opt out from this experiment, I would request you to contact Atlassian support, they will help you out on this and remove the site from the experiment.

Thank you!

[Manja Schledorn]

Please stop this experiment. Apart from the button not being clearly distinguishable and blending in with the +Add buttons, its new place creates a lot of unnecessary scrolling when there's a lot of text in the description field.

Please keep the status button in the right column, where it stays in its place and can be found easily without any scrolling.

[Jakob Klepp]

It's very annoying that for some of my project the issue status is on the right of the screen and for some on the left.

[Karan Sachdev]

This experiment is being carried out for team-managed projects only. It is likely that your other project is a company-managed one.

[Karan Sachdev]

Hey Kris,

You may reach out to Atlassian Support with the feedback. They will check if its feasible to revert this change for individual sites, and will help you out.

Thanks,

Karan