Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-81949

CSV import allow orphan sub-task via External System Import

      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

      1. Create a CSV with only a sub-task to be created, with no parent issue specified
      2. 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

          Form Name

            [JRACLOUD-81949] CSV import allow orphan sub-task via External System Import

            apriscan added a comment -

            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.

            apriscan added a comment - 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.

            Hello!

            We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to fill out this survey. Your feedback will help us learn how we can improve your experience in importing data.

            Survey link - https://forms.gle/NYNkmS92r96z42QV9

            Thanks!

            Prashanth M
            Product Manager, Jira Platform

            Prashanth M added a comment - Hello! We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to  fill out this survey . Your feedback will help us learn how we can improve your experience in importing data. Survey link -  https://forms.gle/NYNkmS92r96z42QV9 Thanks! Prashanth M Product Manager, Jira Platform

            J Lee added a comment -

            Just to add, I ran into this orphaned sub-task issue but the sub-task was NOT created using import via CSV. This was sub-task I created via the web UI. Unfortunately, I'm not sure how this got into this orphaned state. It just happened to be several days ago, I stumbled upon this sub-task without a parent task.

            It's possible that I might have created this as a task and then converted it to a sub-task or something along the line... but I'm not sure. I don't think this bug is solely a CSV import issue. However, the workaround using CSV import to reassign the parent task did work.

            J Lee added a comment - Just to add, I ran into this orphaned sub-task issue but the sub-task was NOT created using import via CSV. This was sub-task I created via the web UI. Unfortunately, I'm not sure how this got into this orphaned state. It just happened to be several days ago, I stumbled upon this sub-task without a parent task. It's possible that I might have created this as a task and then converted it to a sub-task or something along the line... but I'm not sure. I don't think this bug is solely a CSV import issue. However, the workaround using CSV import to reassign the parent task did work.

            S Fong added a comment -

            I agree with the comment made by Antonio above.  I am also facing the same situation recently which I strongly believe that it is not just a feature request and it is a hole as part of the external system import.  This is a major bug since the system shouldn't allow any child (sub-task) to be created without parent if you are entering directly in JIRA.  Then why would you bypass this validation if you are doing External System Import.  This is also another reason why I think the External System Import is very dangerous because it by-passes lots of validation that we should have the system checked before any update is made via this method.  And there's no quick way to revert if the mass update/creation through this method is done incorrectly. 

            S Fong added a comment - I agree with the comment made by Antonio above.  I am also facing the same situation recently which I strongly believe that it is not just a feature request and it is a hole as part of the external system import.  This is a major bug since the system shouldn't allow any child (sub-task) to be created without parent if you are entering directly in JIRA.  Then why would you bypass this validation if you are doing External System Import.  This is also another reason why I think the External System Import is very dangerous because it by-passes lots of validation that we should have the system checked before any update is made via this method.  And there's no quick way to revert if the mass update/creation through this method is done incorrectly. 

            I disagree with the Priority classification: the incorrect creation of an orphan sub-task in NOT a Minor bug...

            Antonio Celso Dias Duarte added a comment - - edited I disagree with the Priority classification: the incorrect creation of an orphan sub-task in NOT a Minor bug...

              e590701def81 Ketaki Kothale
              malmeida Marcus Silveira
              Affected customers:
              14 This affects my team
              Watchers:
              24 Start watching this issue

                Created:
                Updated:
                Resolved: