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

As a user, I would like to update an existing subtask through CSV import

XMLWordPrintable

    • 1
    • 5

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      According to the CSV documentation, you are able to update an existing issue by mapping the issue key on the CSV file to the JIRA field Issue Key.

      However, if you want to update a subtask, you must map the issue key on the CSV file to the JIRA field Issue ID. If you try to update a subtask, JIRA will throw the exception "n of n issues have been skipped because they already exist in destination projects."

      It would great to be able to update a subtask through CSV import.

            [JRACLOUD-64543] As a user, I would like to update an existing subtask through CSV import

            Anusha Rutnam added a comment -
            Atlassian Update - January 2024

            As I did not receive any responses to this comment I am closing this ticket.

            If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - January 2024 As I did not receive any responses to this comment I am closing this ticket. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment -

            I can't reproduce the behaviour described here - my CSV import uses the issue key regardless of issue type and successfully updates the issue (JSW-179 in the following is an existing subtask):

            issue key,summary
JSW-179,new summary

            Do the watchers of this ticket still experience this issue?

            Anusha Rutnam added a comment - I can't reproduce the behaviour described here - my CSV import uses the issue key regardless of issue type and successfully updates the issue ( JSW-179 in the following is an existing subtask): issue key,summary JSW-179, new summary Do the watchers of this ticket still experience this issue?

            Stephan Zehrer added a comment -

            i would be good to be able to all issue based on external sources, xml would be welcome as well.

            Stephan Zehrer added a comment - i would be good to be able to all issue based on external sources, xml would be welcome as well.

            p0cket0m added a comment -

            4 years and nothing happened. 

             

            p0cket0m added a comment - 4 years and nothing happened.   

              Unassigned Unassigned
              Anonymous Anonymous
              Votes:
              5 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: