Sometimes when tasks are resolved or closed, you want to make sure that they will not be modified any more. In this article I will show you what you can do to disable issue editing functionality using one of Jira workflow properties.
The need for workflow properties
Let’s start with an example of a regular issue screen. If a user has permissions like Browse Projects, Edit Issues, Add Comments and so on, this user will have unrestricted possibility to see the issue task, edit all fields and add comments.
What can you do as Jira Administrator to enable these permissions only during the ‘To Do’ and ‘In Progress’ status categories, but not when an issue resolved or closed? This can be achieved by modifying the workflow which is used for this specific issue type. You do not have to do it for all workflow unless you want to disable editing in the 'resolved' status and that is not always needed.
Modify workflow properties on status Done
Unlike other workflow properties I showed you in the article about ordering transition buttons, to disable issue editing, you need to add a property not on a transition but on a status in your workflow.
Go to Jira Administration / Workflows, select a workflow you want to modify and click on Edit. In the Edit mode, select the status you want to modify and click on the properties.
All you have to do now, when you are in the status properties editing mode, is simply add these two properties:
- jira.issue.editable - false
- jira.permission.comment.denied - true or leave empty
When you finish the configuration, your Workflow Step Properties for status Done should look as below. If you make a typing mistake, you can always delete the wrong property and add a new one again. The order in which the properties are added does not matter.
Save the changes and publish the workflow. You should know that if you have more issue types and workflows in a given project, this modification needs to be done for every workflow separately.
Now go back to your task issue view and test your new configuration.
As you can see on the screenshot above, two changes are visible instantly. Buttons ‘Edit’ and ‘Comment’ are missing. Also, if you try to make any other changes to fields like Epic Link, Description, Assignee, these changes will not be saved.
Disable a workflow transition for non-authorized members
We all know that Jira stores all changes to issues in their issue history. This should be enough for users to understand that if they do any unauthorized change to an issue after it has been resolved, this change will be registered. We could also attach some sort of notification to the returning transition.
Another way is simply to ban non-authorized users from making any change by adding a workflow condition. Just like before, go to Jira Administration / Workflows and select the same workflow as previously.
Select the returning transition and click on the Conditions links. Select the condition ‘User Is In Project Role’
In my example, I selected a role ‘Project Manager’. It is a custom global role which I added in this Jira instance.
When you save and publish the changes, as a result a regular not-authorized user will not be able to see any status buttons on the task issue screen. Only authorized users, i.e. belonging to a role ‘Project Manager’, will be able to see the returning transition.
Before you go…
As you can see, a lot of basic permissions management can be achieved without any additional Jira plugins. If you combine it with well designed project permissions scheme and issue security, this should be enough for most use cases in Jira.