The status button for my Jira project was moved to the Description section of the issue, causing discomfort and disruption for my teammates. This change occurred a couple of months ago, and at the time, it was possible to revert it through an issue layout change. However, I can no longer see such an option. Is it possible to move the field back to context section?
Hello everyone,
Good day! You can watch and vote this feature request: https://jira.atlassian.com/browse/JRACLOUD-96142
Thank you!
Hello All
Welcome to community :)
This is due to the feature as mentioned here : https://community.atlassian.com/forums/Jira-articles/Easier-status-updates-for-work-items/ba-p/3068881
As next steps we can do the following
Thank You,
Prachi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a new product change, and it will be rolled out to all sites in phases throughout this week and the next week.
We don't have a way to revert this change, but if it breaks any functionality, you may report it via a support ticket.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Why is it implemented?
It's not that it breaks something; it's just that Status is a part of the ticket context, so it makes more sense to see it in the context section. Also, in the description section, it gets mixed with other fields and is not that visible, making updating status less convenient..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Daria, thanks for your feedback. I shared it with the teams internally.
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Like... WHY change that? :) Now you got to roll up to top after reading comments to change the status. I know that Atlassian usually does not count "optimizing" the interface to make things easier and quicker to operate while introducing changes, but... for <someone powerful> sake - I back in the years I thought software's job is to make life easier for people who do stuff and use it, not harder and slower.
Where is the optimization factor counted into that?
BTW. Will ever Jira pages become cached? Or will we always be forced to wait for work items to load from scratch no matter nothing changed inside?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Karan Sachdev This is so inconvenient and uncomfortable. Please provide an option to revert this back.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
On my personal and instances I manage the status option is still on the context section.
Your instance might be in trail, contact Atlassian Support on this and also provide feedbac on not lieing this change.
Also see; Easier-status-updates-for-work-items
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.