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

Cloned Stories retain values of Sprint field from parent issue

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Low Low (View bug fix roadmap)
    • None
    • None
    • AgileBoard
    • None

      Summary of Bug

      When a Story that was in some closed sprints (or active sprint) is cloned, the cloned story would retain the values of the Sprint field (even for the closed sprints).

      Steps to Reproduce

      1. Create a Story in a Scrum Board
      2. Place the story in a sprint
      3. Complete the sprint
      4. Clone the Story
      5. The cloned story will still retain the values of the Sprint field

      Additional Findings

      • The cloned story will retain all the values of the Sprint field of the parent issue, including closed sprints and any active sprint

            [JSWSERVER-7307] Cloned Stories retain values of Sprint field from parent issue

            rajigali made changes -
            Link New: This issue duplicates JSWSERVER-19903 [ JSWSERVER-19903 ]

            William Sheboy added a comment -

            Please reopen and then resolve this issue for the Cloud version of Jira.  Cloning an issue which was in a prior sprint still copies the sprint information. 

            Unlike other agile work management tools, there is no way to select/ignore which fields are cloned and the defaults to not seem to make sense.

            Thank you for your prompt and relevant action!

            William Sheboy added a comment - Please reopen and then resolve this issue for the Cloud version of Jira.   Cloning an issue which was in a prior sprint still copies the sprint information.  Unlike other agile work management tools, there is no way to select/ignore which fields are cloned and the defaults to not seem to make sense. Thank you for your prompt and relevant action!
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2852753 ] New: JAC Bug Workflow v3 [ 2933908 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544124 ] New: JAC Bug Workflow v2 [ 2852753 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549202 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544124 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 908641 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549202 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 746877 ] New: JIRA Bug Workflow w Kanban v6 [ 908641 ]
            mtokar.adm made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 459816 ] New: GreenHopper Kanban Workflow 20141014 [ 746877 ]
            John Garcia (Inactive) made changes -
            Link New: This issue duplicates GHS-6541 [ GHS-6541 ]
            Peter Obara made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

              Unassigned Unassigned
              jtye Joe Wai Tye (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: