You can't associate any scheme to a project when you only have administrative project permission, you must be a jira administrator. We are working in a project tab that shows to the project administrator the current associated scheme, but he won't be able to change it.
Hello my name is Sergio OAT Solutions, a partner of Atlassian in Brazil.
This is bad and makes no sense, because with Administrate project permission I can select all the other schemes (eg issue type scheme, workflow scheme) of my project.
With this limitation our client who is testing profield could not use it. We are using Project Creator plugin to allow users who are not jira administrators for create projects and thereafter would select the schema profield, but with this limitation only administrator users can select the schema and this blocks the use of profield.
Do you have any plans to change that? Would you do some customization specific to that customer?
I don't understand how can you change the schemes with administrate project permission because Jira doesn't avoid it by default.
Anyway, we have been thinking about your question and we will implement it in the next version of Profields.
Thank you for your feedback.
We are suffering a little delay with the new release. We are preparing the documentation and other web resources. Please, check the email and the market in a couple of weeks. We hope to have it already launched.
Sorry for the inconvenience and thank you for your interest.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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