Jira workflow properties tricks and cheat sheet





You can use work flow properties to put some restrictions on a cretin action/status or transition. 

There are two type of workflow properties

Transition Properties : are key-value pairs that can be used to further customize transitions. For example, transition properties can help to extend a copied system workflow to allow language translations.

Status Properties : are key-value pairs that can be used to restrict users on editing issue fields , attachment, links, comments and much more  on a specific status

Example: You want to allow that only a specific user can edit issue once status is Done.
  • Login as a JIRA Administrator
  • Navigate to Administration > Global Settings > Workflows or search workflows by shortcut press two time .
  • Edit the required workflow
  • Select the Done status and click on property
  • Enter values as
    • Property Key: jira.permission.edit.user         
    • Property Value: username which you want to allow
  • Publish the workflow,now only test user can edit the jira issue once status is done.



Cheat sheet for Jira workflow properties

Property Possible keys Property Value Description
jira.field.resolution. Include, exclude resolution ids It will excluded/include provided resolutions in a transition
jira.i18n. Submit,title i18n property key Translate jira transitions.The translations of those strings have to be stored in the language packs. Here is described how to do this.
jira.permission.edit. group, user, assignee, reporter, lead, userCF, projectrole value of provided key. For example groupname name As per the provided values only they can edit issues on a specific status
jira.permission.link. group, user, assignee, reporter, lead, userCF, projectrole value of provided key. For example groupname name As per the provided values only they can link issues on a specific status
jira.permission.comment. group, user, assignee, reporter, lead, userCF, projectrole value of provided key. For example groupname name As per the provided values only they can comment issues on a specific status
jira.permission.modifyreporter. group, user, assignee, reporter, lead, userCF, projectrole value of provided key. For example groupname name As per the provided values only they can change the reporter on a specific status
jira.permission.workissue. group, user, assignee, reporter, lead, userCF, projectrole value of provided key. For example groupname name As per the provided values only they can log time on issues
jira.permission.assign. group, user, assignee, reporter, lead, userCF, projectrole value of provided key. For example groupname name As per the provided values only they can change assignee on issues
jira.permission.attach. group, user, assignee, reporter, lead, userCF, projectrole value of provided key. For example groupname name As per the provided values only they can add attachments
'jira.permission.manag ewatcher list.' group, user, assignee, reporter, lead, userCF, projectrole value of provided key. For example groupname name As per the provided values only they can add attachments
jira.permission.viewvotersand watchers. group, user, assignee, reporter, lead, userCF, projectrole value of provided key. For example groupname name As per the provided values only they can view watchers list
jira.permission.worklogdeleteall. group, user, assignee, reporter, lead, userCF, projectrole value of provided key. For example groupname name As per the provided values only they can view watchers list
For more information you may visit

About Author
Muhammad Ramzan  is a certified Atlassian Consultant having 10+ years of professional experience in the area of DevOps, Software Testing(Manual/Automation) and Atlassian Tools Administration

0 Comments