I have a project in Jira where users create tickets and attach documents at creation. Once past a certain point in the workflow we want to lock down the ticket so it cannot be editted and attachments cannot be updated (deleted and attached).
The ticket lock down is working as expected with only the listed group being able to make changes:
jira.permission.edit.group = GROUPNAME
But the attachment lockdown is not working to prevent deletions:
jira.permission.attachdeleteall.group = GROUPNAME
Do I have something incorrect or does this functionality not exist anymore?
I tested this out in JIRA 7.4.2. I found that I actually had to use two different workflow properties to lock this down in the workflow versus the permission scheme:
In both cases I set the property value to be a group such as 'jira-administrators'.
I then tested this by having different users add attachments to the issue. I found that when the issue was in this specific state, only 'jira-administrator' group members had the ability to delete attachments from that issue. Without both of these, it still looks like the user that originally uploaded the attachment still has the ability to remove it.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs