-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
Severity 2 - Major
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Epic Name is declared as mandatory when creating/editing or moving a issue, but it's possible the field is stored null/empty
Steps to reproduce:
- Create a non epic issue
- Change issue type to Epic (not moving the issue but selecting the issue type and selecting Epic from the options)
- Changed issue will now have an empty Epic text value
- Trying to edit/save the new issue will trigger the proper validation, but the value in the database will still be null
- Software board show the text as in unlabelled-ISSUE-KEY
- is duplicated by
-
JRACLOUD-36167 Required fields are not set when issue type is changed by inline edit.
- Closed
- is related to
-
JRASERVER-63804 Epic Name can be saved as empty when changing issue type
- Closed