I don't think it is a good idea unless it also locks the field from being used by another project or a particular context version of the field can be managed. Otherwise there is too big a chance someone will delete a value being used by another project. especially since the documentation says there is no warning the value is in use when deleting like there is with the build in editor.
I've got the same worry.
Part of it is experience - almost every Jira site I've been to has started with a project to clean up the mess made by allowing too many administrators. You'll generally find that project leads are ok when limited to their own project (like components and versions) but they will make a total mess of shared fields. I really wouldn't install anything like that!
Hey Support - Just wanted to chime in here about a plugin I ran across in the 'free' section on a local 6.3.1 install. It claims to allow you to delegate permission to users/groups to update the values in a custom field. I just set it all up last night so I'm not sure how well it works, or even how it works, but it is a feature long time missing from JIRA. Here's the name and URL: Jira Customfield Editor Plugin
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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