Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-12196

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

    XMLWordPrintable

    Details

    • 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.
    • Current Status:
      Hide
      Atlassian Status as of 7th Sep 2017

      Hi all,

      We're excited to announce that the ability to split issue is available in JIRA Software 7.5 starting from today!
      We really appreciate your patience with this feature request, and apologize for our silence on the matter.

      As we've mentioned before, our Cloud and Server deployment options are now on separate roadmaps (read more here), but this is a great example of a new feature shipped in cloud, that was popular and prioritized with server customers, that we have brought into server.

      JIRA Software 7.5 is now available to download so you can start planning your upgrade straight away!
      Learn more in our release notes.

      Cheers,
      Jakub Lazinski
      Product Manager, JIRA Server

      Show
      Atlassian Status as of 7th Sep 2017 Hi all, We're excited to announce that the ability to split issue is available in JIRA Software 7.5 starting from today! We really appreciate your patience with this feature request, and apologize for our silence on the matter. As we've mentioned before, our Cloud and Server deployment options are now on separate roadmaps ( read more here ), but this is a great example of a new feature shipped in cloud, that was popular and prioritized with server customers, that we have brought into server. JIRA Software 7.5 is now available to download so you can start planning your upgrade straight away! Learn more in our release notes . Cheers, Jakub Lazinski Product Manager, JIRA Server

      Description

      We strictly use Fibonacci story point values by the book. When the development team is working on an issue we encourage them to break it down into smaller pieces for their work and to give a more granular burn-down but without impacting the committed-to volume of the agreed whole. Presently the clone function is used for this but then further tweaking is required to adjust the story points of the clones and original issue. This causes some noise on the burndown chart and in the respective reports this looks like lots of scope change events but it isn't - it's scope neutral. Also the clones don't inherit the original's workflow state of, in our case, "commissioned".
      We would very much appreciate the possibility of a "split" function, which would provide a dialog box to enter a summary for each of the new issues, inclusive of the original. It should also be possible to enter directly in that dialog the Story Points which each of the new issues, including the original, should have. This must total the same as the story points of the original. On pressing OK, the new issues would be created and the original adjusted in its summary and story point value. All issues created should automatically have the same state and assignee (as well as other meta data such as components, labels, sprint etc.) as the original did prior to the split. All of this should be registered as a single split action on the reports and be completely invisible on the burndown chart.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              icatley Ian Catley
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: