Hi,
I want only a group of people have permission to edit JIRA Feature ticket description. Is there a way to set such permission?
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".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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",
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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Where are you stuck on implementation?
Yes, you can limit edit to a group - check the permission scheme.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi guys, I am struggling to understand the logic here. I am also trying to do something similar, but I don't want to restrict the technicians from viewing the original request. Please see my thread here - https://community.atlassian.com/t5/Jira-Service-Desk-questions/Editing-of-a-created-ticket/qaq-p/998487#U998496
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.