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

As a user I would like to quickly duplicate an issue to split a story into two

XMLWordPrintable

    • Hide
      Atlassian Status as at November 2016

      This feature is now available in JIRA Software Cloud.
      https://confluence.atlassian.com/jirasoftwarecloud/using-your-scrum-backlog-764478062.html

      Show
      Atlassian Status as at November 2016 This feature is now available in JIRA Software Cloud. https://confluence.atlassian.com/jirasoftwarecloud/using-your-scrum-backlog-764478062.html

    • 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.

          [JSWCLOUD-4542] As a user I would like to quickly duplicate an issue to split a story into two

          Martin (Inactive) added a comment -

          This Suggestion previously shipped to the Cloud platform. To keep track of the Server equivalent please follow JSWSERVER-4542

          Kind regards,
          Martin
          JIRA Software

          Martin (Inactive) added a comment - This Suggestion previously shipped to the Cloud platform. To keep track of the Server equivalent please follow JSWSERVER-4542 Kind regards, Martin JIRA Software

          Martin (Inactive) added a comment -

          This feature is now available in JIRA Software Cloud.
          https://confluence.atlassian.com/jirasoftwarecloud/using-your-scrum-backlog-764478062.html

          Kind regards,
          Martin
          JIRA Software

          Martin (Inactive) added a comment - This feature is now available in JIRA Software Cloud. https://confluence.atlassian.com/jirasoftwarecloud/using-your-scrum-backlog-764478062.html Kind regards, Martin JIRA Software

          Russell Webb added a comment -

          Coming from Rally, where we heavily used the functionality of creating child stories, this is the most frustrating problem I have with Greenhopper. I know I can clone and make new stories, but I really want to be able to leave the original story intact and work on the child stories (and have the status of the child stories bubble up to the original). This helps with inspect/adapt as we can revisit how we broke down older stories.

          Russell Webb added a comment - Coming from Rally, where we heavily used the functionality of creating child stories, this is the most frustrating problem I have with Greenhopper. I know I can clone and make new stories, but I really want to be able to leave the original story intact and work on the child stories (and have the status of the child stories bubble up to the original). This helps with inspect/adapt as we can revisit how we broke down older stories.

          Jonathan Boarman added a comment -

          This is such a common task as one takes an overly complex user story and splits it into one or more user stories. In fact, it would be ideal to even have hierarchy to reflect the parent stories. But, if we could just easily duplicate an existing story to assist in splitting the story, it would be helpful in offering value and reducing friction within the tool.

          Jonathan Boarman added a comment - This is such a common task as one takes an overly complex user story and splits it into one or more user stories. In fact, it would be ideal to even have hierarchy to reflect the parent stories. But, if we could just easily duplicate an existing story to assist in splitting the story, it would be helpful in offering value and reducing friction within the tool.

            Unassigned Unassigned
            miruflin Michael Ruflin
            Votes:
            7 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: