Understanding that only project roles with administer project permission is able to add and delete the selection list on the project-specific select field (addon). But we do not want the teamleads who creates workspace/branch to administer the jira project.
Here is our usecase. We have a field called 'Workspace' which is project specific select field. We want the project role Team Leads, should be able to manage this field but do not want this project role (Team leads) to administer (modify components,fixversions etc) the project. Let me know how if you can help me with any workaround. Thanks in advance!
You could create a field which would read values from an external source out of Jira(by Rest call or database call) then make a custom interface to manage the values in the external source. You can make such a field using nFeed plugin. Sounds like a lot of work.
You could also make a custom interface in Jira which would create field layouts for different projects and add options to the field. The custom interface would work from an admin user. There is also much work to do.
I can not see a quick win solution.
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs