Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-6541

Ability to clone an issue without cloning Agile sprint information

    XMLWordPrintable

Details

    • 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

    • 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 Software Cloud. Using JIRA Software Server? See the corresponding suggestion.

      Original summary Cloning an issue also clones Agile sprint information

      Attachments

        1. bonfire-screenshot-20121106-150204-662.png
          bonfire-screenshot-20121106-150204-662.png
          228 kB
        2. postfunction.png
          postfunction.png
          42 kB
        3. SNAGIT.png
          SNAGIT.png
          10 kB
        4. SNAGIT.png
          SNAGIT.png
          53 kB

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-10548 Cloned issues inherit the Completed Sprint value and can't be removed

          • High - High priority issues
          • Closed

          Suggestion - JSWCLOUD-10694 Allow issue to be removed from completed sprint

          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-7307 Cloned Stories retain values of Sprint field from parent issue

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-9835 Cloned Issue is appearing in the Active Sprint

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-10682 Do not include completed sprints when cloning issues

          • Low - Low priority issues
          • Closed

          Suggestion - JSWCLOUD-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

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

          • Closed
          is related to

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

          • Closed

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

          • Closed

          Suggestion - JSWCLOUD-13625 Add "Create Linked Issue" option to Software Projects

          • Closed

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

          • Closed

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

          • Closed
          relates to

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

          • Closed

          Suggestion - JRACLOUD-43019 Option to purge the sprint field while cloning issues

          • Closed

          Suggestion - JSWCLOUD-11770 When cloning issues, clone the position in the backlog

          • Closed

          Activity

            People

              Unassigned Unassigned
              nmuldoon Nicholas Muldoon [Atlassian]
              Votes:
              351 Vote for this issue
              Watchers:
              268 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: