What adds to the frustration is that we were par of the "test group" and I've contacted support to explicitly exclude us due to mentioned issues. It seems like the feedback we provided to defend our request never got any attention as I see the same comments now that the feature is live - either make it optional, or configurable.
This has become a great source of frustration for users in my organization. They are getting confused regarding where things like checklists and links are located. This also adds extra work for admins as we have gotten several messages asking the same question of how to disable or where their buttons are located now.
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.
In our case we found the drop-down list includes redundant items (we have disabled whiteboards), and that without that item in the list we *should* get the individual buttons instead of the horrible "Add" button.
You can follow and vote for the backlog item here: JRACLOUD-85144
If they fix this it won't help orgs that use whiteboards :-\
Atlassian Team members are employees working across the company in a wide variety of roles.
November 5, 2024 edited
Hi Everyone,
Thank you for sharing your feedback on the recent UI changes. I understand that these updates have impacted your workflows, and I genuinely appreciate your candid responses and suggestions.
The decision to adjust the quick add on menu stemmed from two main considerations. First, feedback from many users indicated that the previous issue view was overly cluttered, which led to confusion and increased cognitive load, decreasing ease of use. Second, with the continued growth of the Atlassian suite, the prior design, originally built for a limited set of buttons, struggled to keep pace with our expanding array of objects, products, and integrations. This has impacted both usability and discoverability across the issue view.
We are closely reviewing your suggestions around pinning or favouriting essential actions to enhance accessibility and maintain the speed you rely on.Your feedback is instrumental as we continue refining this experience, and we’re committed to making improvements that align with your needs.
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.
As others have mentioned here, We have a lot of negative feedback from our users about this sudden UX change. We expect similar negative feedback for the other UX changes in the pipeline if we dont have a better way of ease our users into it.
I triage jira bug tickets and ship them to dev teams backlogs all day long, and am constantly dealing with large numbers of duplicate issues which require me to link the issues, as well as migrate over attachments and relevant information included in the duplicated ticket. Additionally I'm formatting the body of tickets all day, every day. Now every action I take to do my job takes 2+ clicks: formatting text, adding an attachment, linking a ticket. This is really frustrating and inconvenient. Please reconsider, or at the very least make this an optional setting.
I keep wondering if Atlassian just needs more experienced Product Mangers and Designers or if top-down management is strangling their ability to deliver.
Even if the mess of this change wasn't self-evident, a day of user testing would have revealed the issue. Maybe user testing is just a checkbox item for them now 🤔
If this managed to pass user testing because the wrong test audience was used, a small pilot roll-out would have triggered the response we're seeing here … just on a much smaller scale.
Come on, Atlassian, we're all trying hard to stick with you. Work with us.
To add another vote for this. I was trying to add a goal to an issue and thought the feature wasn't enabled for some reason. Turns out it's located under "Apps". This really doesn't a whole lot of sense and requires another round of thought and iteration.
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 comments here reminded me that Atlassian has yet to add a keyboard shortcut for "Link issue" which is another suggested feature you might want to follow and vote for JRACLOUD-74885.
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.
Before we had some handy dandy buttons readily available, each with their own singular purpose. Now we have a "+ Add" button and justfucking oodles of empty space doing nothing.
And when I click on the "+ Add" button I get all the buttons that used to be readily available.
This is not an improvement. Please Atlassian. Function over form!
I voted for it: pinning by admins on project-level and users on the user-level looks like a good solution. There is indeed so much empty space, and so much lost in speed and awareness if the space is not used.
I also voted to add keyboard shortcuts for "linking" issues you mentioned, despite it would not solve the biggest problem with hiding the "Link" button: If users no longer see the button, they'll use it less. Shortcuts are only useful for superusers who use Jira so much that they know how to use it and want to use it more quickly.
@Ahmud Auleear would be great if you could add that link to the main article, since it's buried in the second page of comments
This change has resulted in tickets not being linked properly (instead of proper links users are just adding links in comments or description fields as they can't immediately see the link button). You've hidden away key functionality that should be 'in your face' for a user. At least allow this feature to be toggled on / off as we didn't have a clutter problem to solve in our organisation and i would expect many others to be in a similar position.
41 comments