As Sagar Jaid said above, if there were any proper work to be done on this status and resolution fields, it should have been to make the field customizable just lke any other field, in the Project settings > work item layout settings, (or is it in the Screens settings...? after years of new features, this relic of ticket view/layout customization is still around).
This would have been the change that would have been welcomed and gotten them lots of kudos.
But atlassian being atlassian, they made the one change nobody needed or asked for (or can someone, anyone, point to a an actual feature request among the trillion of requests, where someone complained about the status on the sidebar, and hundreds or thousands of people upvoted it?)
Considering how their "research" and "user test" for the new navigation confused quantitative with qualitative data, I'm not sure how trustworthy is whatever test they did to definitely decide the Status had to move to the main column.
My guess: a few days ago I saw that the sidebar had a new feature to switch from showing the comments on the sidebar instead of the context fields. (That must have been some A/B test because I don't see the option anymore.) With that UI, the status of the ticket was not visible at all while in the "show comments in sidebar" mode. So I guess some genius then thought that moving the Status to below the summary was the change needed.
Last but not least.. the last few months they just keep talking about the new redesign being about consistency... and as of right now the Status button has moved to the middle column in Jira software but is still on the right column on Jira Service Management (both company-managed and team managed), so... great job?
Are the developers at atlassian so afraid of tackling the monster of technical debt that this platform must be, that they only find silly minor changes to focus on?
PS: any effort and energy spent in dealing with whatever atlassian breaks next should probably be spent in moving away from this platform, instead
Please. Bring back the status field to the sidebar. Changing the status after adding a comment requires unnecessary actions, which collectively take way more time then they used to. Bad decision, please bring the old position (or at least option to do so) back. Thank you.
UPDATE: I quit the page and went back to it and voting is back to active. This happened to me before. So if anyone is interested in voting https://jira.atlassian.com/browse/JRACLOUD-96247 and it shows it’s inactive, try backing out and relinking to the ticket or refresh your page.
ORIGINAL COMMENT: Is it just me or is the voting for the issue requesting they make the status button configurable now closed? Every time I’ve looked at the ticket it had the option to remove my vote. Now it’s greyed out and inactive.
The issue is less left vs right, but why is the status no longer persistent at the top. It used to stay locked above the pinned fields. Now when we scroll through lengthy issues, we have to scroll all the way back to the top to select a different status.
That may seem like a small thing, but the inconvenience adds up.
Just fix this to 'lock' the button at the top so it always shows.
I'm the Jira Admin for my organization and this change went down like a lead balloon. I have had so many angry Jira users. The stream of complaints on it is now daily. I have sent mail's added banners advising this was NOT requested by our Org and that we have no idea why Atlassian think it's a good idea to now make us scroll up to change the status on the ticket. This is probably the worst change I have seen from Atlassian in a long time and very disappointing especially on the back of the positive UI change earlier this year. What's worse is that you are not listening to the 90% of people who hate this change. The people in my organization who decide which applications we use are also unhappy that your able to change the UI we are using to fit a small number of your clients without consultation or consideration. Maybe ADO might be the way forward :(
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
An except from the Mirriam-Webster dictionary, 2035 edition:
Atlassian (ətˈlæsiən)
1. verb - to create something useful, effective, or otherwise valuable and then destroy it through self-inflicted and entirely avoidable negligence, mismanagement and/or obstinacy.
2. noun - a company founded in the early 2000's around a suite of B2B work management tools; saw it's zenith in the late 2010's before spectacularly self-destructing in the mid-to-late 2020's.
Edit: added my comments to https://jira.atlassian.com/browse/JRACLOUD-96247 instead. Dave Meyer and Ahmud Auleear are going to get a rude awakening based on the C-suite contact escalations I see advocated for in that ticket.
Status under the Tile is so hard to find and see. Not to mention all the data that is relevant to status is in the detail sections. This feature is more than frustrating it make is slower to find useful information. You where rob by whomever did your UX research.
I opened a support ticket about this issue, had a couple of responses saying "please wait while I look in to this" and a link which I cannot access back to the ticket in the customer portal. Within 24 hours of the most recent "I am looking into this" email, I get another one, apparently from that person's manager, saying that it is waiting on me, and they haven't been able to reach me "for some time" and they will close it in 5 days.
The persistent head-in-sand approach is not going to help.
Most of us here are Admins of our respective instances, so we are speaking on behalf of dozens, or hundreds, or thousands of users *each*. Many of us will have advocated for Jira time and time again, and we do remember a time when it was relatively stable and flexible enough to get done what we needed. To be lied to by a product team claiming they want to make things better for "all users" by applying a change on a single product, thereby confusing the hell out of those who have to work between Jira Software and Jira Service Management projects...is just beyond belief.
It's about time the Product team was made responsible for updating the supporting documentation that we are forced to rely on when changes get applied without a thought as to the real world impact. Atlassian documentation for Jira still references "Issues" rather than "Work Items" and still shows pathways from the old UI which no longer exist. We as admins do not have the luxury of letting our own documentation get so badly out of date and maybe, if the product team were to sort this out as well, then a) at least we would be able to look up what has happened THIS time and b) it might give them longer to remember to TELL us you're about to do something in the first place.
Most of us here are Admins of our respective instances, so we are speaking on behalf of dozens, or hundreds, or thousands of users *each*.
When we raise concerns, it's not just our thoughts, but tens or hundreds of other people who raise their concerns through us, but when we add a vote to a ticket asking for a change to be reverted we only get one vote so Atlassian doesn't see all those other people complaining to us.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
The other important thing pointed out by @Kay Bickell is that Atlassian's development work is outpacing their ability to update their documentation. That is inexcusable for such a large company with so many end users who depend on accurate documentation. It's one thing if I don't update my internal documentation for 150 users but quite another for Atlassian who has who knows how many hundreds of thousands of end users.
Atlassian: you need to slow down the rate of UI changes to ensure that documentation is updated when a change is released.
440 comments