Degraded performance Customers may experience issues using Community search. Our team is investigating.
We want to do jira.permission.editable.projectrole= Project_Supervisor but as we see, the projectfole needs a number. So, lets say it is jira.permission.editable.projectrole= 10567.
Our projects have the same role. So as we replicate a new project on the JIRA instance, in order for this workflow to work, the number MUST be the same - we can not be going into the workflow and altering that number. How can we gaurantee that the number is the same?
The best solution is that the jira.permission.editable.projectrole takes a name.
We also can not use a group because the group name changes per project.
I have seen the link jira.permission.editable.xxx as Step Property but this does not solve it.
The numbers you mean are actually the IDs of the Project Roles. The IDs will be the same throughout JIRA, not matter which project. You can see this with the following query in JIRA's database:
SELECT id, name FROM projectrole;
id | name -------+------------------------ 10000 | Users 10001 | Developers 10002 | Administrators 10100 | Service Desk Customers 10101 | Service Desk Team
I hope this helps!
That depends on what you mean by 'copied to Instance B'. If you're planning on copying the instances using a database backup or an XML backup (JIRA's native backup utility), the IDs will remain the same. If you'll simply recreate the same thing on the new instance, the IDs will be different (except for the Users, Developers and Administrators roles, which are default).
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG