Details
-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
19
-
Severity 3 - Minor
-
1
-
Description
Issue Summary
Next-gen projects allow the creation of custom fields with the same name used as some system fields such as:
- Linked Issues
- Issue Type
When doing so, a generic error will be thrown in when creating new issue types. The issue type will be created but without any of the default fields.
Environment
- Only affects Next-gen projects.
Steps to Reproduce
- Create an issue type with one of the above names (i.e: "Issue Type")
- Try creating an issue-type in the same project
Expected Results
- Issue-type is created or Jira blocks the usage of the system field name
Actual Results
The Issue type is created without any field and the following error is thrown.
Despite the error, is still possible to use the NG issue type and add other fields.
Notes
There may be other names breaking although we haven't received reports yet.
Workaround
Change the name of the field to something different
Attachments
Issue Links
- is duplicated by
-
JSWCLOUD-18561 If a custom field with the same field name exists in a Next-Gen project, new issue types cannot be added
- Closed
- mentioned in
-
Page Loading...