[JSWSERVER-6541] Ability to clone an issue without cloning Agile sprint information

Type: Suggestion
Resolution: Fixed
Fix Version/s: 2016-02-22 Cloud, 7.2.0, Available in JIRA Software Cloud
Component/s: None
Labels:
- 1a
- affects-cloud
- affects-server
- clone
- pse-request
- sprint
- sw-c
- sw-clone
- triaged
Environment:
EACJ

Current Status:

Hide

Atlassian Status as at 30 August 2016

This feature is now available in JIRA Software Cloud and JIRA Software Server 7.2.

Kind regards,
Martin
JIRA Software

Show
Atlassian Status as at 30 August 2016 This feature is now available in JIRA Software Cloud and JIRA Software Server 7.2 . Kind regards, Martin JIRA Software
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.

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

Original summary Cloning an issue also clones Agile sprint information

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

bonfire-screenshot-20121106-150204-662.png
228 kB
06/Nov/2012 11:04 PM
postfunction.png
42 kB
21/Jan/2014 12:36 PM
SNAGIT.png
10 kB
20/Jan/2014 4:28 PM
SNAGIT.png
53 kB
20/Jan/2014 4:28 PM

causes

JSWSERVER-10548 Cloned issues inherit the Completed Sprint value and can't be removed

Closed

JSWSERVER-10694 Allow issue to be removed from completed sprint

Closed

is duplicated by

JSWSERVER-5098 Cloning an issue already part of a RapidBoard sprint yields the clone being included in that sprint as well, be it an active or a finished one.

Closed

JSWSERVER-6701 Issues retain their sprint information, when moved to another project

Closed

JSWSERVER-7307 Cloned Stories retain values of Sprint field from parent issue

Closed

JSWSERVER-9835 Cloned Issue is appearing in the Active Sprint

Closed

JSWSERVER-10682 Do not include completed sprints when cloning issues

Closed

JSWSERVER-10866 Cloning a resolved issue in a sprint, copy also the completed sprint field

Closed

JSWSERVER-7707 As a user I want to be able to clone a ticket already assigned to an active sprint but given the option not to include it in that sprint or instead place in top of backlog

Closed

JSWSERVER-9556 Clone a ticket should ask where to place new (cloned) ticket.

Closed

is related to

JSWSERVER-12196 Split an issue and its story points into parts whilst maintaining state

Closed

JSWSERVER-13625 Add "Create Linked Issue" option to Software Projects

Closed

JSWSERVER-10935 Ability to move an issue without copying Agile sprint information

Gathering Interest

relates to

JRASERVER-41150 Update Clone Issue Docs to include or link to JIRA Agile caveats

Closed

JRASERVER-43019 Option to purge the sprint field while cloning issues

Closed

JSWCLOUD-6541 Ability to clone an issue without cloning Agile sprint information

Closed

JSWSERVER-11770 When cloning issues, clone the position in the backlog

Closed

LOLCATS-440 Loading...

SW-3157 Loading...

was cloned as

JSWSERVER-19903 Ability to clone an issue without cloning Agile sprint information

Closed

derives: SW-2614 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(5 is duplicated by, 3 is related to, 6 relates to, 1 was cloned as, 1 derives, 16 mentioned in)

Form Name

Renata Dornelas made changes - 22/Jan/2025 12:24 PM

Remote Link

Original: This issue links to "Page (Atlassian Documentation)" [ 128709 ]

PASQUIET, ROMAIN added a comment - 14/Nov/2019 7:47 AM

It seems to work with Jira server 7.13.3.

When cloning issue, just make sure option "Clone sprint value" is disabled. I thought it was an option for story points, but it isn't.

PASQUIET, ROMAIN added a comment - 14/Nov/2019 7:47 AM It seems to work with Jira server 7.13.3. When cloning issue, just make sure option "Clone sprint value" is disabled. I thought it was an option for story points, but it isn't.

Stefan Singman added a comment - 14/Nov/2019 6:32 AM

Please reopen this issue. It is still a problem in Jira v7.13.5 server version.

Stefan Singman added a comment - 14/Nov/2019 6:32 AM Please reopen this issue. It is still a problem in Jira v7.13.5 server version.

PASQUIET, ROMAIN made changes - 07/Nov/2019 8:42 AM

Comment

[ +1
We use Jira server 7.13.3 and this feature is not available.
The only check box I have when cloning is the option for the "sprint value", but no check box about the sprint assignement. ]

Katherine Yabut made changes - 19/Sep/2019 5:59 AM

Workflow	Original: JAC Suggestion Workflow [ 3070304 ]	New: JAC Suggestion Workflow 3 [ 3663245 ]
Status	Original: RESOLVED [ 5 ]	New: Closed [ 6 ]

rajigali made changes - 26/Feb/2019 12:09 AM

Link

New: This issue was cloned as ~~JSWSERVER-19903~~ [ ~~JSWSERVER-19903~~ ]

Scott Thurston added a comment - 07/Feb/2019 10:13 PM

Reopen issue and please fix this for the Jira server version.

Scott Thurston added a comment - 07/Feb/2019 10:13 PM Reopen issue and please fix this for the Jira server version.

William Sheboy added a comment - 20/Dec/2018 3:37 PM

Please reopen and then resolve this issue for the Cloud version of Jira. Cloning an issue which was in a prior sprint still copies the sprint information.

Unlike other agile work management tools, there is no way to select/ignore which fields are cloned and the defaults to not seem to make sense.

Thank you for your prompt and relevant action!

William Sheboy added a comment - 20/Dec/2018 3:37 PM Please reopen and then resolve this issue for the Cloud version of Jira. Cloning an issue which was in a prior sprint still copies the sprint information. Unlike other agile work management tools, there is no way to select/ignore which fields are cloned and the defaults to not seem to make sense. Thank you for your prompt and relevant action!

Owen made changes - 21/Nov/2018 7:02 AM

Workflow

Original: Confluence Workflow - Public Facing v4 [ 2626842 ]

New: JAC Suggestion Workflow [ 3070304 ]

Rachel Lin (Inactive) made changes - 08/Feb/2018 7:14 AM

Workflow	Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2326800 ]	New: Confluence Workflow - Public Facing v4 [ 2626842 ]
Status	Original: Closed [ 6 ]	New: Resolved [ 5 ]

Assignee:: Unassigned

Reporter:: Nicholas Muldoon [Atlassian]

Votes:: 351 Vote for this issue

Watchers:: 277 Start watching this issue

Created:: 06/Nov/2012 11:04 PM

Updated:: 22/Jan/2025 12:24 PM

Resolved:: 29/Aug/2016 10:21 PM

Details

Description

Attachments

Attachments

Issue Links

Forms

Activity

Collapse comment: PASQUIET, ROMAIN added a comment - 14/Nov/2019 7:47 AM

Expand comment: PASQUIET, ROMAIN added a comment - 14/Nov/2019 7:47 AM

Collapse comment: Stefan Singman added a comment - 14/Nov/2019 6:32 AM

Expand comment: Stefan Singman added a comment - 14/Nov/2019 6:32 AM

Collapse comment: Scott Thurston added a comment - 07/Feb/2019 10:13 PM

Expand comment: Scott Thurston added a comment - 07/Feb/2019 10:13 PM

Collapse comment: William Sheboy added a comment - 20/Dec/2018 3:37 PM

Expand comment: William Sheboy added a comment - 20/Dec/2018 3:37 PM

People

Dates

Backbone Issue Sync