Very easy, see this code:
Read MorePermissions 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
New plugin for JIRA: New Status Colors FREE
New colors for two kind of status [red] for “Cancel” or “Cancelled”, “Suspend” or “Suspended”, “Reject” or “Rejected” and [orange] for “Wait” or “Waiting”, “Hold”, “On Hold”, “Pause” or “Paused”. Only you need to create the new status using this names.(containing one of this words,i.e. for word “Waiting”: “Waiting for Customer”, “On Waiting”, …). This…
Read MoreNew Listener change status of an issue depends of the type of the issue created in JIRA
How to Hide the “Configure Fields” Button on the Create Issue Screen in JIRA
Copy this code in the description of a custom field (in the Field Configuration linked to the project) Result:
Read MoreSSO with JIRA & Confluence (Really Trusted Apps) with CROWD and LDAP
1. Configure CROWD Define in CROWD in the internal directory this groups (with the CROWD UI): confluence-administrators crowd-administrators site-admins system-administrators … something group with the same name such as JIRA/Confluence teams New internal directory in CROWD with the JIRA & Confluence internal users and assign the groups. ( this step must be done automatically importing directly the users…
Read More
www.MrAddon.com ®: Jira & Confluence Administration Support Blog 