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

When cloning issues, clone the position in the backlog

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Resolved (View Workflow)
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • 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.

      Description

      A common workflow for us is it create a high-level story that may affect multiple components. As we get closer to a sprint where the work will actually be done, the story may get split into multiple smaller stories for each component. We currently use the clone feature to do this which has the benefit of creating links between the different stories.

      The biggest frustration with that method is that when we clone a ticket, it is created either at the bottom of the backlog or the bottom of the current sprint (depending on where the originating ticket is). When the backlog is large, it is frustrating and time consuming to drag the issue back to its correct space. It'd be very nice if the newly cloned issue were inserted in the same place as the original.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              hulstjos Joshua Hulst
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: