Secure Statuses from being renamed or deleted

[Andrew Henders]

Hi,

Is there any plugin or customisation that can restrict global and system administrators from modifying or deleting the globally used "Status" objects in JIRA Data Center? The accidental modification of the Status object has wide-ranging effects on all Projects but it can be so easily modified; it really is a risk.

Any suggestions or examples on how this could be achieved would be very much appreciated.

Thanks,

Andrew Henderson

[Fabio Racobaldo _Herzum_ · Accepted solution]

Hi @Andrew Henders ,

unfortunately you can't limit that feature. A Sys Admin/Admin should have enough information to verify impacts about this change. Moreover there are some alerts during that operation.

Fabio

[Alan Stephenson · Accepted solution]

Hi

never heard of one. That role of system admin needs that ability to add statuses when creating new workflows. Policy is to educate your system admin. A good system admin should know this.

-alan

[Megaport Ops]

Thanks for the feedback.

For mine, such a core object should be made read-only when already in use in any workflow; prevention is better than the cure etc. But it looks like a couple of feature requests and bugs have been raised on this topic but have been dropped.

Cheers again.

[Nic Brough -Adaptavist-]

The requests have been dropped because they're asking for a technical fix for a human problem.  The real fix is to have administrators who understand what they are doing, not have code block them from doing their job.