Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-43019

Option to purge the sprint field while cloning issues

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Duplicate
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Feedback Policy:
      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.

      Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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

              Assignee:
              Unassigned
              Reporter:
              jose.martinspinheiro Jose M.
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: