Why do I select a Screen when I create a Transition?

I am creating a Workflow.  I added a new Transition, and one of the fields was "Screen" - I am not sure what it means to associate a Screen to a Transition.

1 answer

1 accepted


if you need to get some input from the user when transitioning the issue, like for example when starting development you might want to learn how many days it will take to solve, then you can add a custom field to a screen and add this screen to your transition. but you don't have to add a screen, it is not compulsory. it is up to your operation.

so the selected screen (if there is one) is shown when the transition occurs?  Who is it shown to?  The user who caused the transition?

yes exactly, it is shown while the transition occuring and shown to the user who is making that transition.

For example: 

When one of our engineers moves a Bug to 'Completed' we want them to enter information into the Cause and the Solution fields. We have a screen with those two items on it as required fields. That way we always get that information filled out.

To expand on this slightly, the screen can be used to fill in missing information that would otherwise cause it to fail a validator.  The screen is shown when the transition is selected (which means it has already passed any Conditions on the transition), but before any validators are executed.  Any data supplied or changed while on the screen will be the data seen by each validator. If the screen is cancelled, the transition does not execute and you remain in the original state.

A very typical example is that a "Resolve Issue" transition generally includes a screen that allows one to select the "Resolution".  A "Close Issue" transition that is after "Resolve Issue" does not, but a "Close Issue" transition that happens before "Resolve Issue" does, so as to also behave like "Resolve Issue".

An example going the other way is that you can use post functions to set the resolution depending on the transition; if you do that, you don't need a screen, and if you have a screen, you wouldn't want to also include that field.

Finally, in particular for the "Resolution" example, you can use workflow properties to restrict what resolutions are available on that screen, by setting them on the transition.


Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,265 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot