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

As a Sprint Planner I want to be prompted for the new name of my sprint (problems with multiple boards)

XMLWordPrintable

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

      This problem comes up during multiple sprint planning across same projects. Users would like to be prompted before GreenHopper guesses what sprint name they'd like.

      Eg:

      1. Create a scrum board for "Project 1", and "Project 2" called "One"
      2. Create another scrum board for just "Project 1" called "Two"
      3. Go to board "One", create a sprint called "Asterix" and start it
      4. Go to board "Two", create a new sprint - it will be auto named "Asterix 2"

      Instead 4. should prompt the user what to call the sprint if it's being planned on a different board.

      It is understood that once the sprint has been triggered to start it prompts the user to name it then along with the sprint start and end dates.

            [JSWSERVER-9658] As a Sprint Planner I want to be prompted for the new name of my sprint (problems with multiple boards)

            Michael Tokar added a comment -

            pjp,

            The JIRA Agile Team has a very large backlog. As such, it only hinders our ability to plan when we retain large numbers of issues. We also believe it is disingenuous to our users and customers to leave issues open that we are not likely to address.

            There is always the possibility of re-opening such issues. However in this particular case I don't see us addressing your issue. The creation of a new planned (future) sprint is designed to be a very lightweight process. The editing of the name of the sprint is very simple. Introducing additional steps to this flow goes against our intentions for simple design.

            I hope you understand. Thanks again for reporting the issue.

            Regards,
            Michael Tokar, JIRA Agile Team

            Michael Tokar added a comment - pjp , The JIRA Agile Team has a very large backlog. As such, it only hinders our ability to plan when we retain large numbers of issues. We also believe it is disingenuous to our users and customers to leave issues open that we are not likely to address. There is always the possibility of re-opening such issues. However in this particular case I don't see us addressing your issue. The creation of a new planned (future) sprint is designed to be a very lightweight process. The editing of the name of the sprint is very simple. Introducing additional steps to this flow goes against our intentions for simple design. I hope you understand. Thanks again for reporting the issue. Regards, Michael Tokar, JIRA Agile Team

            Pat Pigatti added a comment -

            Hi,
            I don't think moving this to Resolved status was the correct thing to do here since it wasn't resolved. It's okay if it's deferred further in the roadmap but it shouldn't be resolved. Not an acceptable practice and not something we do for our customers. Please keep this open.

            Thx.
            Pat

            Pat Pigatti added a comment - Hi, I don't think moving this to Resolved status was the correct thing to do here since it wasn't resolved. It's okay if it's deferred further in the roadmap but it shouldn't be resolved. Not an acceptable practice and not something we do for our customers. Please keep this open. Thx. Pat

            Michael Tokar added a comment -

            Many thanks for reporting this issue. Realistically, we are not planning on addressing it in the next 12 months.
            Regards,
            GreenHopper Team

            Michael Tokar added a comment - Many thanks for reporting this issue. Realistically, we are not planning on addressing it in the next 12 months. Regards, GreenHopper Team

              Unassigned Unassigned
              mandreacchio Michael Andreacchio
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: