-
Bug
-
Resolution: Cannot Reproduce
-
Medium
-
15
-
Severity 2 - Major
-
3
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Summary
Required fields are not set when Issue Type is changed by an Inline Edit
Steps to Reproduce
- Take a standard JIRA installation and add a field, e.g. "Detection Phase", to Bug issue type. Make the field required in the field configuration.
- Create an issue of some other type.
- Change the type to Bug via inline edit.
- Result: The required field has no value.
Expected Results
Required fields are propmted to be updated
Actual Results
Issue type can be changed via inline edit and required fields are not populated.
Another example: Changing an issue type to Epic via inline edit does not require an "Epic Name" to be set
Workaround
- Use the More > Move Function to change the issue type
- duplicates
-
JRACLOUD-63804 Epic Name can be saved as empty when changing issue type
- Closed
- is duplicated by
-
JRACLOUD-39849 Leaving required field empty when changing task type from "New Feature" to "Epic"
- Closed
- is related to
-
JRASERVER-36167 Required fields are not set when issue type is changed by inline edit.
- Gathering Impact
- relates to
-
JRACLOUD-36946 Edit Screen not updated when Issue Type changed
- Closed
-
JSWCLOUD-16334 Converting issues to Epics leaves the Epic Name field without a value
- Closed