Permissions based on Workflow Status in JIRA

In the Workflow transition properties you can set diverse permissions restrictions like this: jira.permission.comment.group=group jira.permission.comment.denied=true/false jira.permission.edit.group.1=group1 jira.permission.edit.group.2=group2 jira.permission.modifyreporter.user=username jira.permission.delete.projectrole=10000 jira.permission.subtasks.delete.projectrole=10000 jira.permission.close.user=username jira.issue.editable=false … You can see more permissions and terminology in this link  

Read More

Workflow properties

jira.field.resolution.exclude Resolution id Add comma-separated resolution ids to the transition properties where you want to not show certain resolutions jira.field.resolution.include Resolution id Add comma-separated resolution ids to the transition properties jira.i18n.submit i18n property key Transition (usage: action submit button name) jira.i18n.title i18n property key Transition (usage: action name, etc.) jira.issue.editable true, false Configuring Workflow Step jira.permission.*…

Read More

JIRA trick: Set one more category status color! The “undefined color” (black color)

To see one category status color more, you need only: Go to the JIRADB Database Execute SQL: SELECT * FROM jiradb.issuestatus; In the status you need “black color” set the field “STATUSCATEGORY” to 1 That’s all! Supported colors (in the standard) Field Summary Fields Modifier and Type Field and Description static String COMPLETE static String IN_PROGRESS…

Read More

[SOLUTION] The issue lost the workflow transaction buttons and when the issue is moved an ERROR is triggered

Launch the Integrity checker from the Administration view “Check Workflow Integrity” ( in order to avoid timeout on the web transaction, is good option connect to the original IP:PORT of the JIRA for example: http://127.0.0.1:8080) If when the issue is moved an error is raised like “duplicate key entry…“, the best option is launch this instruction in…

Read More