I really hope we can roll this back. We have a large team that uses these tickets, and changes like this cause a lot of heartburn with no real upside. It also means changing a lot of our training materials every time we have a largely cosmetic change like this. It has an impact across the organization that is not worth it for us. And honestly, it looks terrible from a user standpoint. It clutters up an already busy area.
As a person with ADHD, I have, already and on more than one occasion, been in the middle of reading a comment, realized that I should update the status of a ticket, then had to scroll back to the top of the ticket to change the status so as to not forget, then had to find my place again.
Prior to today, this is something I could do without even having to look away from what I was reading.
It was frustrating enough when the active comment box became sticky in a way that it would often cover a large portion of what I would need to scroll to in order to review different information present in a ticket I was working on, but this is extremely workflow-breaking.
This update rolled out to my organization, or at least my instance, this morning, and I've already become frustrated to the point I've had to stand up and stretch multiple times.
Before this update, meta information was always available when looking at the ticket contents and comments.
This change article has been out for roughly a week and has already amassed around 5 pages comments that are almost exclusively people asking for this to be changed back or have the option to be changed.
The only update to the article itself was an acknowledgement that this is not something that Atlassian is interested in rolling back despite this.
There are new complaints about this being workflow-breaking every 20-30 minutes.
I'd be interested to see the factors and results of the A/B testing that was mentioned multiple times, as I have trouble believing that robust usage of JIRA would make this change even marginally desired.
I understand and appreciate the intent behind this change as well as that you made it with data driven analysis. That said, I do not find that it improves my experience. Instead, it has made my experience worse.
It would be nice if this was something users could position. The previous location for me was much more intuitive and user friendly. It allowed me to make status changes easier. I am having to scroll back to the top more often now to make those changes.
In short, I really wish you would reconsider rolling this change back until it can be something users themselves have control over. I do not believe this was a positive change.
this is NOT the appropriate way to "announce" such a significant change. i've been fielding frantic emails and calls from panicked users who are in the middle of critical actions for a launch and can't promote any of their work items.
If you want to make changes then I get that, but TELL YOUR USER BASE - don't hide it in a forum.
I liked the Status in the previous location because when you scrolled down the page in the work item on the left side of the page, the Status remained fixed on the right side. Now, when you scroll down the page, you can no longer see the Status of the item.
Regardless of the value of the change, such a significant change should be highlighted with a roadblock pop-up. Existing users were asking if they or the client company had somehow created a misconfiguration. It should not be on the client company admins to field queries about changes they didn't make and didn't even know about.
But I'll quote a former colleague: "Change is always bad. Only sometimes not changing is worse." This was not one of those times.
@Ahmud Auleear reading through the comments, it seems like the problem people have is not necessarily with the location of the button, but with the fact that it's not longer visible when scrolling the content area. For what it's worth, that would be the same problem on the sidebar as well for work items with lots of fields.
With that being said, a quick fix for this problem could be to move the status into the sticky header once it becomes sticky. That way it's still accessible as one of the main actions on the work item.
The way I see it is, if we have a quick update that a user needs to do in Jira, the components in the right panel would do them.
The centre of any story deals with the requirements and items that we'd take additional steps to finish, like adding a sub-task or adding a link to the story etc., using the "Add" button right below the title of the story.
Quick changes like "Status updates" or "Change assignee" or add "Fix versions" etc are generally 2-click items and were rightfully placed in the right panel.
Now it is hard to keep sight on the "Status" of the story with this change.
141 comments