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

Using an old key when updating Issues through CSV changes the pkey

XMLWordPrintable

      Issue Summary

      If you upload a CSV file with old Issue Keys, the Issues will change their project associated

      Steps to Reproduce

      1. Create an Issue in a project (P1-123)
      2. Move that issue to another project (P2-456)
      3. Do any changes through a CSV import by using the former Issue key (P1-123) & former project
      4. The change is successfully made but the project key is changed to the original one (P1-456)

      Expected Results

      No project key changed or showing an error that the user should use the new issue key

      Actual Results

      The project key is changed

      Workaround

      Currently, the only workaround is to bulk move the changed Issues back to their right project

            [JRACLOUD-81978] Using an old key when updating Issues through CSV changes the pkey

            Matthew Hunter added a comment -
            Atlassian Update - January 29, 2025

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - January 29, 2025 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

            Yatish Madhav added a comment -

            Thanks for reporting the ticket, Omar and Faizan.

            I have tested the steps to reproduce and successfully did so ... the other thing I noticed is that the previous link to the issue key does not redirect. Eg. in the example P2-456, after it is updated via the CSV import, does not redirect to the new 'original' key, ie P1-456) - which I think is ok not to fix, but I hope it is good for you to know while fixing. 

            Thank you

            Yatish Madhav added a comment - Thanks for reporting the ticket, Omar and Faizan. I have tested the steps to reproduce and successfully did so ... the other thing I noticed is that the previous link to the issue key does not redirect. Eg. in the example P2-456, after it is updated via the CSV import, does not redirect to the new 'original' key, ie P1-456) - which I think is ok not to fix, but I hope it is good for you to know while fixing.  Thank you

              Unassigned Unassigned
              ovargas@atlassian.com Omar Vargas
              Affected customers:
              1 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: