how do I add a transition screen to a workflow in Jira Data Center?
- User
how do I add a transition screen to a workflow in Jira Data Center?
Assistant
In Jira Data Center, you can add a transition screen to a workflow transition by following these steps:
-
Navigate to the workflow editor
- Go to Administration (gear icon) > Issues > Workflows
- Find your workflow and click Edit (you may need to create a draft if it's an active workflow)
-
Select the transition
- In the workflow diagram, click on the arrow/line representing the transition you want to add a screen to
- This will highlight the transition and show its properties
-
Add a screen to the transition
- In the transition properties panel, look for the Screen section
- Click Add Screen or the pencil icon next to "Screen"
- Select from available screens in the dropdown menu, or create a new screen if needed
- Click Add or Update
-
Configure screen fields (optional)
- You can choose which fields appear on the transition screen
- Set fields as required, optional, or hidden for this specific transition
-
Publish the workflow
- Once you've made your changes, click Publish Draft at the top of the workflow editor
- If the workflow is associated with active projects, you'll need to migrate them to the updated workflow
The transition screen will now appear when users move issues through that specific transition, allowing them to view or edit the configured fields before completing the transition.
Note: You'll need Jira Administrator permissions to modify workflows. If you're working with a system workflow, you'll need to copy it first before making changes.
-
- User
Does a transition screen need to be included in a screen scheme?
Assistant
No, a transition screen does not need to be included in a screen scheme. Transition screens operate independently from screen schemes.
Here's the key distinction:
Screen Schemes control which screens are used for:
- Creating issues (Create screen)
- Editing issues (Edit screen)
- Viewing issues (View screen)
Transition Screens are:
- Associated directly with specific workflow transitions
- Displayed only when an issue moves through that particular transition
- Not part of any screen scheme configuration
When you add a screen to a workflow transition, you're selecting from all available screens in your Jira instance, regardless of whether they're included in any screen scheme. The screen will appear during the transition even if it's not part of the screen scheme associated with that issue type.
This separation allows you to:
- Use specialized screens for specific transitions without affecting regular issue operations
- Have different fields appear during transitions than what users see when creating or editing issues
- Reuse the same screen across multiple transitions in different workflows
For example, you might have a "Resolution Details" screen that only appears when transitioning to a "Resolved" status, but this screen doesn't need to be (and typically shouldn't be) part of the regular create/edit/view screen scheme.
- User
I'd like to add a some help guide to the field I have applied to a transition screen, I may want to make it mandatory as well. To give context, our users of Jira and pretty poor at assigning a person to ticket. I am adding assignee to a transition screen to prompt user to think about who should now be working on the ticket. Can I make it so the assignee must not be "unassigned" in this transition screen?
Assistant
Yes, you can achieve both goals - adding help text and making the assignee field mandatory (not "unassigned") on your transition screen. Here's how:
Adding Help Text to the Assignee Field
-
Go to Field Configuration
- Administration > Issues > Field Configurations
- Find the field configuration used by your project
- Click Configure next to it
-
Add Field Description
- Find the Assignee field
- Click Edit next to it
- Add your help text in the Description field (e.g., "Please assign this issue to the person who will be working on it next. Do not leave unassigned.")
- This description will appear below the field on all screens where it's used
Making Assignee Required (Not "Unassigned")
You have two options:
Option 1: Workflow Validator (Recommended)
- In the workflow editor, click on the transition
- Click Validators in the transition properties
- Click Add Validator
- Choose Field Required Validator
- Select Assignee field
- Publish the workflow
Note: The standard validator only checks if the field is filled, not if it's "unassigned". For stricter validation, you'll need Option 2.
Option 2: Script Validator (Requires ScriptRunner or similar)
If you have ScriptRunner installed, you can add a more specific validator:
- Add a Script Validator to the transition
- Use a script like:
issue.assignee != null- Add an error message: "Please assign this issue to a specific user. Unassigned is not allowed."
Option 3: Workflow Property (Simple but Limited)
Add a workflow property to make the field required:
- On the transition, click Properties
- Add property:
jira.field.requiredwith value:assignee
This makes the field required but still allows "unassigned" as a valid value.
For the best user experience without additional plugins, combine the Field Required Validator with clear help text that instructs users not to leave the issue unassigned. The validator will at least ensure they interact with the field, and your help text will guide them to select an actual user.
-
- User
The comments box comes up by default in the transition screen, can I get rid of this?
Assistant
Yes, you can remove the comment box from transition screens. The comment field appears by default on many transitions, but you can control this.
How to Remove Comments from a Transition Screen
- In the workflow editor, click on the specific transition
- Look at the transition properties panel
- Find the Options or Properties section
- Look for a checkbox or property called "Add Comment" or "Show Comment Field"
- Uncheck this option or remove the property
Alternative Method - Transition Properties:
If you don't see a checkbox option:
- Click on the transition
- Go to Properties in the transition panel
- Look for any property like:
jira.field.commentjira.field.comment.required
- Delete these properties if present
If Comments Still Appear:
Some transitions (especially system transitions like "Resolve" or "Close") have comments built-in by default. For these:
- Check if there's a "Comment" field explicitly added to your transition screen
- If so, edit the screen and remove the Comment field
- Some built-in transitions may have the comment field hardcoded - in these cases, you might need to create a custom transition without the comment functionality
Note:
The exact location of these settings can vary slightly between Jira versions, but the comment field behavior is typically controlled either through transition properties or as part of the transition's configuration options.
If you're still seeing comments after trying these steps, it might be worth checking if there are any post-functions or conditions that are adding the comment field programmatically.
- User
I have quite a few transitions to apply this screen and validator to, is the bulk approach or will it have to be one at a time?
Assistant
Unfortunately, Jira Data Center doesn't provide a native bulk editing feature for workflow transitions. You'll generally need to apply screens and validators one transition at a time through the UI. However, here are some approaches to make this more efficient:
Semi-Bulk Approaches:
1. Copy Transitions (Within Same Workflow)
When editing a workflow, you can:
- Configure one transition completely (screen + validators)
- Some versions allow you to copy/duplicate transitions with their configurations
- Look for a "Copy" or "Duplicate" option when right-clicking transitions
2. Workflow XML Export/Import
- Export your workflow as XML
- Edit the XML file to replicate the transition configurations
- Import the modified workflow
- Caution: This requires careful XML editing and testing
3. ScriptRunner Bulk Operations (If Available)
If you have ScriptRunner, you can use the Script Console to programmatically update multiple transitions:
// Example script structure (would need customization) import com.atlassian.jira.workflow.WorkflowManager // Script to add screen and validator to multiple transitions4. REST API Approach
Use Jira's REST API to programmatically update workflow transitions, though this requires development effort.
Most Practical Approach:
For most administrators without scripting tools, the fastest method is usually:
- Open the workflow editor
- Keep your screen and validator selections ready
- Click through each transition systematically
- Apply the same screen and validator configuration
- Use keyboard shortcuts where possible to speed up navigation
While it's repetitive, manually configuring each transition ensures accuracy and typically takes less time than setting up and testing automated solutions for a one-time configuration task.
Tip: Make a checklist of all transitions that need updating to ensure you don't miss any.
- User
Are radio buttons in Jira single select?
Assistant
Yes, radio buttons in Jira are single select - users can only choose one option from the group of radio buttons.
Radio Button Behavior in Jira:
Single Selection Only: When you create a custom field with radio buttons, users must select exactly one option. Selecting a new option automatically deselects the previous choice.
Field Types for Radio Buttons:
- Radio Buttons - Single select only
- Select List (single choice) - Also single select, but displays as a dropdown
If You Need Multiple Selections:
For multiple selections, you would use:
- Checkboxes - Allows multiple selections
- Select List (multiple choices) - Multi-select dropdown
- Labels - For free-form multiple values
Creating a Radio Button Field:
- Administration > Issues > Custom Fields
- Add Custom Field
- Choose Radio Buttons
- Configure the options
- Add to appropriate screens
Radio buttons are ideal when you want to:
- Force users to make exactly one choice
- Display all options visibly (unlike dropdowns)
- Make the selection process very clear
- Prevent multiple selections
This makes them perfect for fields like Priority Level, Environment Type, or Yes/No decisions where only one answer makes sense.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.