Is it possible to use Jira automation to show transition screen when certain conditions are met?

[Francis Calderisi]

Good morning,

Taking a shot in the dark here :) 

Is it possible to use Jira automation (or another method) to display a "transition screen" only when certain conditions are true? 

I am familiar with some of the Validators that can be applied on workflow transitions but haven't quite found what I am looking for.

The goal here is to make a specific field(s) mandatory if the Priority field of a given ticket is set to a certain value.

Any help would be much appreciated.

Thanks

[Trudy Claspill · Accepted solution]

Hello @Francis Calderisi 

What type of project does this concern?

Team Managed projects do not yet support display of transitions screens.

Assuming you are using a Company Managed project, you could create two transitions.

In one transition you would set a Condition for the Priority field value is the value that would make the fields required. In that transition you would add the transition screen and the Validators to make the fields required.

In the other transition you would set a Condition for the Priority field value being not equal to the value that would require the field. This transition would not include the transition screen or validators.

Only one of the transitions will be available to the users, based on the value of the Priority field in the issue.

[Francis Calderisi]

Hello @Trudy Claspill thanks for the input.  I do have one question however.  When you say 2 "transitions" do you mean that I would have to create another transition to the status I want to get to?  Both transitions having their own validator?

I am not sure that I understand the steps that you are proposing here.

Thanks

[Trudy Claspill]

Yes, you would create two separate transitions and each would have its own Conditions and Validators.

For example, let us say I wanted to require fields during the transition from Selected for Development to In Progress, based on the value of Priority.

First, if there is a global transition to In Progress, that transition has to be deleted. Otherwise it could be used instead of the transitions you set up that check the Priority value.

You then add two separate transitions from Selected for Development to In Progress. I named mine Hight Priority and Normal Priority.

On the High Priority transition I add a condition to show this transition only when the Priority field is set to High.

I add Validators for the fields I want to require when the Priority is High.

If I want to allow the user to fill in the Required fields during the transition, then I need to create a screen that includes those field and associate that screen to this transition.

For the Normal Priority transition I set a condition so that it will show when the Priority is not High.

If I need to validate other fields in this case, I would add Validators to this transition to fulfill that requirement. If no fields need to be required/validated in this case, then you don't add any validators.

Because the two transitions have mutually exclusive Conditions, only one transition or the other will be available. The system should not ever show both transitions being available at the same time.

The above solution is predicated on the requirement that the Priority field was set prior to the transition being executed. If you are setting the Priority field on a Transition Screen while you are executing the transition, that would require a different solution.

[Francis Calderisi]

Wow, thanks @Trudy Claspill I will give this a try.  Definitely seems to fit the bill.  My checks will be executed when the ticket is moved to "Done" so for sure the Priority will already be set appropriately.

[Bill Sheboy]

Hi @Francis Calderisi 

Just checking if the suggestions resolved your question.  If so, please consider marking them as "answered" to help others with similar needs find solutions faster in the future.

If not, please respond with additional details so the community can help.  Thanks!

Kind regards,
Bill

[Francis Calderisi]

Good afternoon @Trudy Claspill 

I finally got an opportunity to test your solution.  Unfortunately the Condition I put in place for the Priority field does not seem to restrict the transitions as expected.  Here is my current set up:

I think that I have everything in place as per your example...Any clue to what might be wrong?  Thanks

[Trudy Claspill]

Hello @Francis Calderisi 

Thank you for providing the information about your workflow setup.

What is the Priority field set to for the issue for which you are showing available transitions?

Can you confirm the Type of your project? Get that information from the View All Projects page under the Projects menu, looking at the Type column 

[Francis Calderisi]

Good morning @Trudy Clapsill,

The priority is set to Critical.  And the project is a "Company Managed" project.

Thanks again 

[Francis Calderisi]

Hello again,

I have been running some more tests and there seems to potentially be issues with duplicate fields in our instance.

I used the Assignee field instead and the suggested solution does work correctly.

Thanks @Trudy Claspill for all your help.

[Trudy Claspill]

Yes, having multiple fields with the same name can negatively impact these types of customizations. Did you see more than one Priority field listed when you were trying to create the Condition? If you saw only one Priority field listed, then that would be referring to the Priority field provided by default by the Jira application. If you are using a different field also named "Priority" that may not be available for use in the Condition.

[Bill Sheboy]

Hi @Francis Calderisi 

Atlassian automation rules cannot pause to show a screen, other than for the Manual Trigger to gather inputs before running the rule.

If you do not find what you need from the built-in workflow validators, perhaps check the Atlassian Marketplace for addons of other validator types.

And just to confirm...I do not work for Atlassian or any marketplace vendor.

Kind regards,
Bill

[Bogna Krystian_Deviniti_]

Hi @Francis Calderisi 

I think Dynamic Forms for Jira (Marketplace add-on developed by the company I work for) could be helpful here. It allows you to dynamically show or hide fields based on the values of other fields. So, you can configure it so that when the Priority field is set to a certain value, additional fields become mandatory.

[Francis Calderisi]

Thanks @Bogna Krystian_Deviniti_ but unfortunately add-ons are not an option for me at this time.