-
Bug
-
Resolution: Fixed
-
High
-
22
-
Severity 1 - Critical
-
88
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
When importing a sub-task via CSV, you should require a reference to the parent issue.
If you try to import the CSV via Issues > Import Issues from CSV, that validation is done, however when importing through Administration > System > External System Import the CSV import creates orphan sub-tasks.
Steps to reproduce
- Create a CSV with only a sub-task to be created, with no parent issue specified
- Import CSV using External System Import
Expected Behaviour
A warning message saying "Subtask 'Issue' doesn't have a valid Parent Id selection. Issue will not be created." should be displayed (as it is on "Import Issues from CSV")
Actual behaviour
Issue is created successfully without a parent
Workaround
How to fix orphan sub-tasks
- is duplicated by
-
MIG-359 Lack of parent/sub-task validation in CSV import causes invalid state
-
- Closed
-
-
JRACLOUD-64768 CSV import allow orphan sub-task via External System Import
-
- Closed
-
- is related to
-
JRASERVER-42405 CSV import allow orphan sub-task via External System Import
-
- Gathering Impact
-
- relates to
-
MOVE-128361 Loading...
Form Name |
---|
How come this issue is still happening on Jira cloud and this ticket is closed? I just moved bunch of issues that had subtasks and now the new project is a complete mess. You cannot promote orphans to tasks, you cannot assign the to parents... this is riduculous.