Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

status properties vs project permissions



In our scenario the reporter raises an issue and after that it goes through an approval flow via several issue status. Once this approval started, it should not be possible anymore to edit the issue. (Scenario B: it is only possible for project admins role)

First I allowed the project role "Administrators" and "Reporter" to edit the issue within the project permissions:


then I tried several ways to block editing for certain status via the properties:

Property key: jira.permission.attach.denied
Property value: (empty)


Property key: jira.permission.edit.projectrole
Property value: 10002 (Administrators)


I also tried to limit it to a certain JIRA Group. The result was always the same: If the issue is in the relevant status, the project admins cannot edit the issue anymore but the reporter is still able to edit the issue.
With this setup I would expect, that the blocking overrules the permission within the project permission, but it is not working.

What am I missing here?

Thank you for your help.

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer Atlassian Team Feb 26, 2021

Hi Christopher,

I see that you are looking to try to restrict at which stage a reporter can edit an issue in Jira, and when they cannot.  The workflow properties can still be used to make this work the way you want here.  In my own Cloud site, under the project settings, I went into the workflow in question, found a specific status (I picked 'In Progress'), then clicked the View Properties.

I added the property key of

and the property value of





However there is another step that is needed here that is frequently over looked.  And that is, we need to publish the workflow again after this change is made.  That isn't always as obvious as it should be, I admit.  But if you go back to then edit the workflow itself, you should see a prompt at the top asking you to publish this draft, like so:

Screen Shot 2021-02-26 at 3.47.34 PM.png


If you click that Publish Draft link, you see a dialog like this, you can certainly make a backup of your workflow first, but in this case I did not for my testing purposes.


Screen Shot 2021-02-26 at 3.47.42 PM.png

Once that is done, only site-admins will be able to edit that issue in that workflow when it is in that specific status.

I hope this helps.

Let me know if you have any concerns about this.


Hi Andy,

thanks a lot!

Sometimes the solution is too simple :) Now it works as expected.




Like Andy Heinzer likes this

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you