Now GA - try the new issue transition experience in Jira!

[Travis Sims]

@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.  

[ptraverso]

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"!!!

[Gloria Makinwa]

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

[Nathan Phillip Brink]

@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).

[Fernando Garcez]

Just to point out that the instructions to activate it are wrong, it says:

"

1. In Jira, select your profile picture or initials, then select Personal settings

"

You should click in the cog icon on the left of your picture, took me a while to find it...

[Cedric Weber]

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.

[Rick Westbrock]

Thank you for sharing that, I read the weekly changelog every week and don't recall seeing that Assets fields had been added.