Details
-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
4.4.3, 6.0, 6.4.5, 7.2.2, Archived Jira Cloud
-
4.04
-
7
-
Severity 3 - Minor
-
2
-
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
We haven't been able to reproduce this behaviour in later versions of Jira. The expected behaviour is that changing an issue type is only allowed if the issues share a workflow and field configuration scheme. As such, we will mark this issue as "Not a Bug".
If we've misunderstood, or there are other factors to consider, please comment on this ticket and let us know 
Cheers,
Dave
Atlassian Support
A project is created that has multiple issue types. For one issue type, the Component and Affects Version fields are not required. For another issue type, these two items are required. If you create an issue of the first type that contains no value for component or Affects Version, and then use the bulk operation to move it to the second issue type (staying within the same project), the following behavior is seen:
On the "update fields" screen (step 3 of 4 for the bulk operation), the component and Affects version fields will have a red asterisk, indicating they are required. The "Retain" checkbox will be checked, but will be grayed out so that you can't deselect it. When the user presses the "Next" button, errors will be shown on the Component and Affects Version fields indicating that these fields are required. There's no way to enter a value for these fields, however.
Workaround: bulk-edit the issues to add values for component and Affects Version, then do the bulk-move to change the issue type.
Attachments
Issue Links
- is related to
-
-
- Gathering Impact
-
- relates to
-
-
- Closed
-
-
-
- Gathering Impact
-