In company-managed, Jira Cloud project, I have two workflows (PCR & Change Approval) that need restriction upon completing a card. The first (PCR) workflow works just fine to restrict edit, delete and cloning using the three properties: jira.permission.createclone.denied, jira.permission.delete.denied and jira.permission.edit.denied.
The second (Change approval) workflow has 5 transitions to close and all 5 transitions contain the 3 properties listed above and yet the workflow allows editing cards in the close status. Is there some sort of Jira limitation on properties when there are 5 transitions to the same status?
PCR Workflow:
Change (approval) Workflow:
Hello @Ann Rumenapp
If you want to prevent those actions when the issue is in the Closed status then you need to click on the Status lozenge (not the transition) and add the properties to the Status (not the transition).
When I add the permissions to the Close status it applies to any workflow using that status correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Incorrect.
When you add Properties to a Status in a specific workflow it applies only to that status in that workflow, which will apply it to any issue that uses that workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh awesome! This particular status is used in 80 workflows so I was chicken to update it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.