• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 1
    • 5
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Scenario

      User is performing multiple project imports of projects that belonged to the same board / shared of the same sprint. For each import performed, JIRA creates a different sprint with the exact same name.

      Expected Behaviour

      JIRA would notice that the Sprint already exists throughout the import and not create a new one.

      Workaround

      Bulk edit the issue in the duplicated sprint to the original sprint by referring to the Sprint ID and not name. This will however, impact the reporting for the sprint if its related to an active sprint

          Form Name

            [JSWSERVER-15024] Project Import imports the same sprint multiple times

            this problem happens when you import csv with multiple sprints into Data center. the csv was for only one project

            Carla Ann K. Rowland added a comment - this problem happens when you import csv with multiple sprints into Data center. the csv was for only one project

            Can someone tell me if this is only happening with multiple projects are imported but does not happen if you import the same projects individually ?

            Brian Taylor added a comment - Can someone tell me if this is only happening with multiple projects are imported but does not happen if you import the same projects individually ?

            I just ran into this problem while importing 6 projects, that used a common board (and hence common sprints).

            The users had to spend a lot of time to work the problem around with bulk update.

            At least the documentation should be updated to warn users about this problem - it came out of the blue to me.

            Pavel Boev added a comment - I just ran into this problem while importing 6 projects, that used a common board (and hence common sprints). The users had to spend a lot of time to work the problem around with bulk update. At least the documentation should be updated to warn users about this problem - it came out of the blue to me.

              Unassigned Unassigned
              bpicarelli Benito Picarelli
              Votes:
              10 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: