-
Bug
-
Resolution: Fixed
-
Low
-
5.0, 6.1
-
5
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
A plugin (or JIRA) cannot yet prevent a user from deleting special issue types. When issue types are deleted, JIRA allows the ID to be re-used for another issue type when it is subsequently created.
This causes problems for plugins like GreenHopper, because we store these IDs for special use and are then not notified when they are no longer valid.
- is related to
-
JSWSERVER-8435 Greenhopper requires Epic fields even if unlicensed
- Closed
-
JSWSERVER-6927 If another Issue type exists with default Epic ID, Greenhopper treats it as the new Epic.
- Closed
- relates to
-
JRASERVER-36562 Project templates plugin uses incorrect workflow status id sequence
- Closed
-
JRACLOUD-32277 JIRA should not re-use issue type IDs after they are deleted
- Closed
- was cloned as
-
JRASERVER-34766 JIRA should provide the ability to define system issue types which cannot be modified by administrators
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...