How to restrict Jira ticket description field edit permission

Hi,

I want only a group of people have permission to edit JIRA Feature ticket description. Is there a way to set such permission?

 

 

 

1 answer

Do not show Description on the create screen. Put it on Edit screen or any other transition that will be only visible by specific group or people. So for example .. You can create a transition called "Update Description" add only this field and set up Condition.

When Mirek says "put it on edit screen", he means "do not put it on the edit screen, only put it on transition screens".

Thanks. I don't want to restrict workflow transition but only restrict ticket description field edit to a group of people.The user story is "as a requirement manager, I want feature/story ticket description be editable to requirement managers when ticket is in "open" and "in analysis" status, so that feature/story ticket edit permission is controlled. Is there a way to do this?

Yes.  You do what Mirek says, and move the ability to change the description down into the workflow where you can use conditions to say "only requirement managers can edit this screen".

Thanks. Could you share a step-by-step guide?

Log in as an admin

Go to admin and find the screens section, and add a new screen, putting the description field on it.

Go to the project and find the workflows that are in use.  Edit each one of these.

For each status where you want to allow "edit",

  • Create a new transition that goes back to the same status. 
  • The transition should use your new screen
  • The transition needs a condition like "only requirement managers"

Go to the project and find the "issue type screen scheme" - drill down into that until you find the screen used for "edit".  Remove the description field from it.  (You may need to create a new screen for this if the edit screen is shared with create and/or view)

Thanks. Still not sure how to implement it. By the way, is it possible to set a ticket's all fields edit permission to a group of users?

Where are you stuck on implementation?

Yes, you can limit edit to a group - check the permission scheme.

 

Not clear about the implementation. It seems complex. Does permission scheme support edit control on a couple of ticket types in a JIRA project? I don't want all ticket types have this edit control.

 

Not off-the-shelf, that's why Mirek gave the answer he did.

There is another trick, which is painful to set up and maintain - you can set workflow properties to control the groups which can or cannot edit an issue when it is in a certain state in the workflow. As issue types can be set to use different workflows, you'd need one workflow for each different edit scheme.

Thanks. The trick really helps.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,109 views 13 19
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot