-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
1.1.1
-
None
Deleting an SLA from the left hand side, does not entirely delete the SLA from the drop down when you create a new SLA. This is a separate, but related issue to improvement request JSD-119.
Attached screenshot.
Steps
1. Create SLA
2. Select SLA from list and select "Delete"
3. Create a "new SLA" and hit the drop down.
Item from step 1 is still there when you are doing step 3.
- is related to
-
-
- Closed
-
- relates to
-
JSDSERVER-186 Allow JIRA admins to delete an SLA custom field
- Closed
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-183] Deleting SLA does not remove it from the list of SLAs
@miruflin Understood - BUt if you really make a mistake in the spelling or objective of the SLA JIRA-ADMINS should have the ability to delete it with a double confirmation to understand that it can effect SLAs in other projects.
Also.. Can you delete the attachment that includes the URL in the screenshot. Thanks.
Shane Froebel
added a comment - - edited @miruflin Understood - BUt if you really make a mistake in the spelling or objective of the SLA JIRA-ADMINS should have the ability to delete it with a double confirmation to understand that it can effect SLAs in other projects.
Also.. Can you delete the attachment that includes the URL in the screenshot. Thanks. This is by design.
SLA fields are managed globally and shared between time metrics of the same name across different projects. Currently SLA fields won't be deleted even if all associated time metrics are deleted.
The drop down offers all existing and available fields, with the hope that users reuse existing fields instead of creating lots of fields with similar names in different projects (e.g. Time to resolution vs Time To Resolution vs Time to Resolution).
Attachment deleted. Also, I created
JSD-186to track your request.