-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
10
-
Severity 3 - Minor
-
2
Issue Summary
Issue priority scheme allows to associate with multiple projects making deletion of the priority scheme difficult
Steps to Reproduce
- By default, all the projects are associated with the Default priority scheme
- Create a new priority scheme Scheme 1 and associate a project Acme with it.
- You will see that project Acme should be automatically disassociated from the Default priority scheme once it is associated with Scheme 1.
- Go to Default priority scheme and add project Acme. Now you have 2 schemes associated with project Acme.
- If you go to issue Acme-111 it will start displaying the priorities from the Default and not from Scheme 1
- Try to delete Scheme 1 by disassociating the project Acme
Expected Results
- It should not allow priority scheme to be associated with 2 projects
- It should allow to the disassociation of the project from a scheme (even if there are 2 schemes the project is associated with) and allow to delete the scheme
Actual Results
- It allows one to associate projects with multiple priority schemes
- It does not allow you to delete the scheme if point 1 is true.
Workaround
The current workaround is to disassociate the project using the Priority scheme REST API . Once the project is disassociated you can delete the scheme.