Loading...

XML

Word

Printable

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

Long Term Backlog

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...; Page Loading...

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

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:: 14/Nov/2019 7:47 AM

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

Details

Description

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates