@Arbaaz Gowher Can you add fields in the Jira Workflow automation to check for Zephyr or QMetry linked testing so I can have it check for that before an issue is "Done"? Also, I setup an agent to get URL's from the Jira comments but there is no action to add it to the story by "Add web link". I see other actions in there just not this one.
This new feature is horrible! Destroy all workflows with approvals option! (please you must the way to avoid this change for this kind of workflows)
This type of changes must be optional, not mandatory. Be carefull with the changes that you think are usefull or "great idea".. remember "less is more"!!!
Is there a way to turn off the due date functionality? i've noticed this is now a forced feature meaning i cannot create a ticket without putting in a date which leaves me making up dates just to complete the ticket
@Gloria Makinwa That feature is likely something that your Jira admin turned on for your project. The ability to specify which fields are required for issue creation has been standard functionality in Jira for a long time if not forever. I do not think that this is turned on by default in a newly created project in Jira. So, please work within your organization to change this.
Note that this blog post is about the issue transition screen, not about the issue creation screen. (I think the issue creation screen had been updated to the new GUI long ago but I am not actually sure if I could tell if it were the new or old GUI at this point as a mere user who hasn’t seen the old GUI in a long time).
FYI: Since this article does not get any updates I want to share that excluded fields are now supported. My findings together with the Atlassian support:
We were initially not supporting following types of fields Assets, Services, Customer Organisation, Request Language as per original blog post. These fields are now supported. I have also tested the same on my site.
Seems that also the support relies on reverse engineering to know if things have been rolled out.
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 Champions.
However, with the old experience I used to be able to click "enter" on my keyboard to accept the pre-selected resolution field when transitioning an issue from In Progress to Done. This was a nice speedup for me. Now, I have to mouse over to click the button which adds a few seconds to every transition for me. Since I deal with dozens of replies to tickets a day, that can add up for me.
We would appreciate clarification on the rollout plan for the new issue transition experience. Our app requires this new experience to be enabled, and it is not feasible to ask several hundred users to activate it individually in their personal settings.
Is there an official timeline for when this experience will become the default for all users, or when Jira admins will be able to enable it globally without going through Atlassian Support?
Seems like Atlassian has removed the toggle button from the personal settings tab, does anyone know if this mean the feature is released for all users?
I’d definitely stick with the old issue transitions. But once I’ve enabled it, I’m automatically switched back to the new issue transitions every two months. Previously, you could disable it, but now the buttons to get rid of these dreadful new issue transitions are missing. I can only recommend never enabling this...
These changes are not good. The option to opt out of the change is not available. GIVE US THE CHOICE TO STAY WITH WHAT WE KNOW. We can no longer BULK change due to needing to pick an option and they new way just blocks you completely... stop the changes.
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 Champions.
I have the opposite problem in my environment: I have users stuck on the old experience and with no toggle they can't enable it. I don't think I should have to raise a Support case just to get this enabled for users who want the better editor for keying in customer facing comments when resolving a JSM ticket.
Arbaaz is inactive in the public-facing Jira, do not expect a response here (it is unlikely that Atlassian monitors old threads anyway). The best way forward is to contact Atlassian support if you're on a paid plan.
I just got more info from Atlassian after raising a support ticket:
"The new issue transition experience has now reached General Availability (GA). As part of this mandatory release, the option to revert to the previous experience has been removed; all cloud instances are now on the new transition experience by default. This is why the toggle is no longer visible in Jira Labs."
Atlassian is going to enable the new experience for our Jira Free testing instance after we requested it, and we have published troubleshooting pages for our customers:
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 Champions.
We also had to raise a case with Support to have the new experience enabled for all users. We were in a situation where any users who did not enable the toggle while it was still available were stuck on the old experience with no way to switch. This feels like a botched rollout to me, why would Atlassian remove the toggle without also enabling the new experience for all users?
124 comments