Change management approval workflow stuck at manager level

ALM Atlassian Jira Software
, , , , , , ,
1

We’re experiencing a critical bottleneck in our change management process on Jira 9. Change requests are consistently getting stuck at the manager approval stage and not progressing to the implementation phase.

The workflow transition conditions appear correct in the configuration, but approvals aren’t triggering the next state. When managers click ‘Approve’, the issue status remains unchanged. We’ve verified that the manager role has the correct permissions, but workflow audit logs show no error messages - the transition simply doesn’t execute.

Current workflow configuration:


transition: approval_gate
condition: user_in_role(manager)
post_function: update_status(approved)

This is delaying our entire release cycle. Has anyone encountered similar workflow transition issues with role-based approval gates in Jira 9?

2

Also worth enabling debug logging for workflows. In Jira 9, you can add ‘com.atlassian.jira.workflow’ to your logging configuration at DEBUG level. This will show you exactly why transitions are failing in your atlassian-jira.log file. It’s been invaluable for troubleshooting our workflow issues.

3

Thanks both. I checked the conditions - there’s no ‘Only Assignee’ restriction. However, I found that the target status does have two required custom fields: ‘Implementation Date’ and ‘Technical Reviewer’. These aren’t on the transition screen currently.

4

That’s your issue right there. The transition is failing because required fields aren’t being set. You have two options: either add those fields to your transition screen so managers can fill them during approval, or modify your workflow post-function to set default values for those fields automatically. We went with the second approach using a scripted post-function that sets sensible defaults, then allows the implementation team to update them later.

5

I recommend checking your workflow validator configuration as well. Sometimes validators can block transitions without clear error messages to end users.

6

Are you using custom fields as part of the approval process? We had a similar issue where a required custom field on the target status wasn’t being populated during the transition. The workflow would fail silently without proper error logging. Check your target status screen configuration to ensure all required fields are either populated or available on the transition screen.

7

I’ve seen this before. Check if your workflow transition has multiple conditions that might be conflicting. Sometimes the ‘Only Assignee’ condition gets added by default and blocks role-based transitions. Go to your workflow editor and verify all conditions on that specific transition.