We have a requiremnt about controlling privilege of edit/reconfigure permission schema
AdministratorA create a permission schema and AdministratorB could edit/reconfigure it
AdministratorA create a permission schema and only AdministratorA could edit/reconfigure it, and other administrators couldn't do it.
1. It seems not achiving it through configuration on the page, is it correct?
So, we want to implement it by add-on plugin(servlet filter plugin) which means Java API.
2. Is it possible to get creator of permission schema by Java API, and which Class or Interface is available?
Thanks in advance.
That is the correct behaviour. Your administrators need to be able to administrate the system, and that means having access to change all the config. They don't "own" parts of the system, they have access to all of it.
You won't be able to do this with an add-on, and certainly not with a simple couple of class calls. You'll need to get into the guts of JIRA and add functions to support and implement it.
Taking the example in your second question illustrates it - JIRA does not track or expose any configuration changes, so you'd need to implement that. (It is logged in the audit log, but that's optional, and not a proper "ownership" system)
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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