Summary

• When importing a CSV file, Jira does not perform any type of verification. Because of that, it is possible to change an issue's issue type to an issue type with different workflow / type (e.g. Task issue type to Sub-task issue type), resulting in data inconsistencies.

Details

• Because of this bug, it is possible to change an issue's Issue Type from a TASK issue type to a Sub-task issue type, causing inconsistencies (check JRACLOUD-67480: Lack of parent/sub-task validation in CSV import causes invalid state for more details)
• Furthermore, this error results in Workflow inconsistencies, as the workflow associated in the database does not match the one showed in the UI
  • 
    Note: In this case, the name column describes the workflow actually associated with the issue. By accessing the issue through the UI and clicking View workflow, the workflow displayed is the one defined in the Workflow column

How to reproduce

1. Create an issue with any issue type
2. Create a CSV file to update that issue's issue type, such as the one below:

   Issue Id,Issue Type,Summary
   <Issue Key>,<New Issue type>,,
   

   • Notice that in order to reproduce the bug, the issue type should be one that uses a different workflow in the project
3. Go to System > External System Import > CSV and import the issue in the project

Expected Behavior:

• Jira should not allow the user to update the issue to an invalid issue type

Actual Behavior:

• Jira allows the user to update the issue to any issue type (including a Sub-task issue type, causing the issue to have no parent)

Proposed solution:

• Jira could use the same verification used when trying to edit an issue's issue type through the View Issue screen