Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9556

Clone a ticket should ask where to place new (cloned) ticket.

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • 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.

      If you clone, the cloned tickets goes next the the position of the basic ticket.
      Users want to select, where the new (cloned) ticket should be placed (in a current sprint or in the backlog).

      Main Problem: If you clone a ticket in a running sprint, the reporting (Burn-Down) is completely destroyed. First effort is added and then reduced immediately, if you remove the cloned ticket (just in the same minute it is counted)

              Unassigned Unassigned
              b4129e9f9b81 MM (PREM)
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: