You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I've been trying to restrict edit access for issues at a specific status via the Workflow status properties. I can't seem to figure out what to add to give the "Automation for Jira" user edit access.
I've tried both (not at the same time):
Neither seem to work. I've confirmed that "Automation for Jira" is able to edit the respective issues when I have no properties set. But when I set these properties to try to restrict edit access to ONLY "Automation for Jira", nothing is able to edit the respective issues - including the "Automation for Jira" user.
Something I'm missing?
You have to use
Key: jira.permission.edit.projectrole
Value: ID of the project role of "atlassian-addons-project-access"
This was perfect and took me way too long to find. I could not get these specifics from any of the Atlassian documentation I found. To me it would seem that 'Value' information like this should be easier to find.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The right Automation for Jira ID can get from Quickfilter assignee = Automation for Jira.
Your number format looks correct.
jira.permission.edit.user
557058:f58131cb-b67d-43c7-b30d-6b58d40bd077
Actor of the Automation rule = Automation for Jira.
I tested few cases, it looks this works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I have same need as described initially as Secure level adding is not the choice (Issues must be visible for any project user, but editable for 1 project role (this is clear how to do) and for Automation for Jira only).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try this in status property
Property Key: jira.permission.assign.assignee
Property Value: assignee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Imdad KP
I'm curious, what would this do? The "Automation for Jira" user is not the assignee for the issue (and I don't want to make it the assignee).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you share the screenshot of the configurations you have created? Then, I can share the exact configuration that I have mentioned above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not sure what this screenshot will tell you that my original post didn't, but here you go:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I ended up getting close enough to what I need for now using Security Levels. It's not perfect and I may need to revisit this in the future, but I'm going to call it good enough for now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.