How can we disable the new Admin->Add field in JIRA 6.1 ?
We have given admin access to some of the project leads. Since it's very easy to create the field now they are all trying it ;-) The concern here is fields are created in Global contexts and getting added to shared screens, so it's impacting other projects.
Thanks in advance!
You can disable it by disabling the module "View Issue Ops Bar Actions group" in Issue Operations plugin. Though it's a system plugin I didn't notice any issue by disabling it. You may test it thoroughly before trying in production.
You know that disables it for all administrators? And doesn't stop the function from working if you get there via another route?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes I know it will disable it for all administrators and doesn't stop admins from creating a customfield with Add Customfield UI.
Actually, my answer was not to address the real problem of multiple jira administrators but just to disable that particular menu item from the UI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Or you could hide the link using script. Pasted into the Announcement Banner.
// Disable Admin/Add Field option AJS.$("#opsbar-admin_more").live("click", "#add-custom-field", function(){ jQuery('#add-custom-field').hide(); });
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can't disable it.
There's a general piece of advice on admin here - never give it out to project leads and other users. You should have a small handful of administrators (at least two, never more than ten, and ten is when your Jira install is huge)
I would remove this access from them as soon as possible. Every Atlassian job I've had has started with being hired to sort out the mess made by too many admins.
(Atlassian are looking at more granular admin access levels, but I don't know exactly when to expect an improvement)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
AFAIK "Add new field" is the default permissions to the adimins so we can't change this. But you can do one thing tell to the project leads if add any new fields then need to configure to that particular project only and issue types then it will not effect the other projects.
Hope this helps you,
Patina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.