NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Creation of new SLA metrics should be restricted. It's creating a new customfield each time a Project Admin makes one.
This can easily get out of control with more and more Service Desks, and then your custom field name space becomes whacky.
This impacts areas such as JQL where autocomplete list looks super-long.
- is related to
-
JSDSERVER-186 Allow JIRA admins to delete an SLA custom field
- Closed
- relates to
-
JSDCLOUD-116 Allowing project-admins to make new SLA metrics is bad for administrators
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-116] Allowing project-admins to make new SLA metrics is bad for administrators
Mark Love
added a comment - +1 totally agree.
Administration of service desk is a mess at the moment. Creation of unnecessary SLA custom fields that can't then be deleted is causing all sorts of usability problems for us.
Mark Love
added a comment - +1 totally agree.
Administration of service desk is a mess at the moment. Creation of unnecessary SLA custom fields that can't then be deleted is causing all sorts of usability problems for us.
JIRA administrators can now block project admins from creating SLA custom fields, as well as clean up any unused SLA fields in the system.
More details are in the documentation for Managing SLA data.
Cheers,
Gilmore