How to Set Up Jira Workflow Approvals, Required Fields, and Conditional Transitions (2026)

Lead

Jira workflows enforce approvals, require specific fields at transitions, and route work conditionally,keeping tickets well-formed and ensuring the right people sign off before work progresses.

Quick answer:

• Add approval steps to gate transitions by role or group
• Use validators to require specific fields when moving between statuses
• Set conditions to show/hide transitions based on field values or user role

Verified against Atlassian Cloud Jira workflows on 2026-05-04.

Prerequisites

How ScaleIT handles this: See Jira Rescue

• Jira Cloud or Jira Service Management Cloud project
• Project admin permissions
• 10–15 minutes per workflow pattern

Approvals

Add an Approval Step

1. Go to ⚙ → Projects → [Your Project] → Settings → Workflows
2. Click the workflow name to open the editor
3. Select the transition you want to gate (e.g., "Submit" → "Approved")
4. Scroll to Conditions → Add condition → User is in group
5. Choose the approver group (e.g., "Change Advisory Board")
6. Scroll to Validators → Add validator → Comment is required
7. Click Publish draft

Only users in the selected group see the transition button. They must add a comment to execute it.

Multi-Step Approvals

For manager → security → finance approval chains:

1. Add three statuses to the workflow: "Awaiting Manager Approval," "Awaiting Security Review," "Awaiting Finance"
2. Create transitions between them, each with a condition: User is in group → select the appropriate group (Managers, Security Team, Finance)
3. Publish the draft

Tickets visibly progress through each stage, showing which approval is blocking progress.

Required Fields on Transition

Require Specific Fields When Transitioning

1. Go to ⚙ → Projects → [Your Project] → Settings → Workflows
2. Click the workflow name and select the transition (e.g., "Start Progress")
3. Scroll to Conditions → Add condition → View this screen
4. Select or create a screen with the fields you want required (e.g., Assignee, Sprint)
5. Mark those fields as required in the field configuration for your issue type
6. Scroll to Validators → Add validator → Field is required
7. Select each required field and click Add
8. Publish the draft

Agents now see a pop-up screen and cannot transition without filling those fields.

Conditional Transitions

Show/Hide Transitions Based on Field Value

1. Click the transition you want to gate
2. Conditions → Add condition → Value field match
3. Choose the field (e.g., Priority), select "equals," and enter the value (e.g., Critical)
4. Click Add

The transition button only appears if Priority = Critical.

Show/Hide Transitions by User Role

1. Click the transition
2. Conditions → Add condition → User is in group
3. Select the group (e.g., "Change Managers")

Only members of that group see the transition.

Block Transitions Until Sub-Tasks Are Done

1. Click the transition (e.g., "Ready for Deploy")
2. Conditions → Add condition → Sub-tasks resolved

The transition is hidden until all sub-tasks are marked Done.

Conditions, Validators, and Post-Functions

• Conditions: Determine if the transition button is visible. If a condition fails, the user doesn't see the option.
• Validators: Check that input is valid before the transition executes. If it fails, an error blocks the transition.
• Post-Functions: Run after a successful transition. They update fields, send notifications, or log events.

Use all three for a complete workflow gate: conditions as gatekeeper, validators as checkpoint, post-functions as cleanup.

Verify

• Attempt the transition as a non-approver. The button should be hidden.
• Attempt as an approver. The transition should complete.
• For required fields: try transitioning without filling them. An error should block it.
• Check the activity log. It should show approver, timestamp, and any comments.

Troubleshooting

Transition button is hidden or missing

• Check the workflow editor for overly restrictive conditions. Verify group membership in ⚙ → User management → Groups.

Can't publish the workflow

• A condition references a deleted field or non-existent group. Open the workflow draft and remove the failing condition. Check group names are exact and case-sensitive.

Button visible but error on click

• A validator is failing. Check the error message to identify the missing field. Either fill it before transitioning or remove the validator if it shouldn't apply.

Multi-step approval skips a status

• Add a condition requiring group membership to each approval transition. Check that automation rules aren't bypassing the workflow.

Next Steps

Workflow design saves weeks of rework and prevents tickets from moving forward without the right oversight. If you're managing approvals manually, tracking required fields in spreadsheets, or dealing with tickets that slip through, your workflow needs tightening.

ScaleIt designs and optimizes Jira workflows for MSPs, IT teams, and professional services firms. We handle approvals, validators, and conditional routing so your team focuses on running work instead of worrying about control. Reach out for a free consultation.

Verified against Atlassian Cloud Jira workflows on 2026-05-04. Vendor docs: https://support.atlassian.com/jira-software-cloud/docs/what-are-approvals/, https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/, https://support.atlassian.com/jira/kb/require-field-edit-when-transitioning-the-status-of-a-jira-work-item/