I found this in the documentation:
I'm trying to limit by project role who can edit the issue. It appears I need to know the Project Role ID to do this. Where is that found?
It is this part that is my problem. I understand I should have jira.permission.edit.projectrole for the property but I don't know where to find the ID # (2 in the example) for my project. I assume it is added at the end either as a tag on projectrole2 or as projectrole.2 or something that works.
@Evgenii thanks for getting me aligned on the project role ID. I've updated the Status Property by using this:
Do you know if this works with a transition as well? Will that lock out editing for the rest of the workflow as opposed to setting it for every transition?
It appears to be the case. Thank you again for your help.
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.
@Evgenii thanks for checking back here. I'm hoping you can shed some more light on my issue.
I was able to restrict editing to one role but a use case came up that I thought could be solved by having the property contain two project roles but it doesn't allow you to create two property entries for the same Status.
I tried a number of variations and found that none of these worked as intended. I used <role ID1, role ID 2>, <role ID1; role ID 2>, and <role ID1/role ID 2>.
I was wondering if I just didn't have the syntax correct. I also suspect I may have to use the plain jane edit property to specify users to make it work. Any thoughts?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Got it. You can't set list of roles, but you can set 2+ more properties.
But there is small trick, you have to set properties with ids, like:
jira.permission.edit.projectrole.1
jira.permission.edit.projectrole.2
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.
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.
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.