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

Option to purge the sprint field while cloning issues

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Duplicate
    • None
    • None
    • 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.

    Description

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

      We often clone issues and move them to other probjects, where the sprints to not belong to the boards, but currently it isn't possible to exclude the sprint field from cloning. This would be the best solution, since a sprint is planned within the sprint planning and is not used for defining by reporters.

      The next problem is, that currently it is not possible to remove closed sprints by editing the issue. The only workaround provided by Atlassian is to use the bulk operation and remove the sprint id. But this is just a workaround and needs to be handled with care.

      Please improve the clone operation and offer an option to purge the sprint field, similiar to the option to include attachments or links. This should work, even when the sprints are closed alread, becuase the clone is a new issue.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              d24cdaee3f9e Jose M.
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: