| Table of Contents |
|---|
| Info | ||||
|---|---|---|---|---|
| You will need the following JIRA plugins:
| |||
Level: INTERMEDIATE |
Problem
Once in a while it happens that we want to lock an issue, where by lock I mean that only the assignee of that issue can play with it. There's an open ticket about this with Atlassian, and Power Actions™ helps resolve it.
This example shows you how to do that by using Blitz Actions Power Actions™ and the Issue Security Scheme.
...
Now you're probably wondering "Why do i need Blitz Actions Power Actions™ to do this? Why can't the user set the security level himself?". Well, there are a number of reasons for this; what if we don't want the assignee to have the "Set Issue Security Level" permission? Or what if we don't want them to be able to edit the issue at all, but only log work or comment on it? Even if they do have the "Set Issue Security Level", not having "Edit issue" permission will prevent them from locking the issue.
...
Now let's get working. First off, we must create the security level, which looks like this:
Create the actions
Once we've done that, it's time to create the actions. We will create two actions Lock and Unlock.
For the conditions, we will disable the Lock button if the security level is already Locked, and disable the Unlock button if the security level is empty. Of course, we will only show the buttons to the current assignee.
...
That's it! Now let's test it.
| Note |
|---|
Instead of current assignee, we could set the value of a user picker as the allowed user, and change the value of the custom field to the current user when locking an issue, thus resolving a common problem exposed here: https://jira.atlassian.com/browse/JRA-6146 |
See also
- Disabling inline edits in Jira
- Forbidding users to create some issue types
- Hide fields from users not in a project role
- Limit Number of Characters in Text Field
- Lock an issue - a better variant (Live Fields)
- Making an issue read-only
- Require an issue to have attachments
- Require User to Log Work Before Transitioning Issue
- Restrict issue type availability by user
- Restrict workflow based on status of dependencies
- Validator for component lead