Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-1502

Support Per Issue/Subtask "Maximum assignees per story"

    XMLWordPrintable

    Details

    • UIS:
      15
    • Support reference count:
      1
    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

      As a project manager I need to be able to set the number of assignees per story for each story to correctly project out the tentative release date and team capacity.

      For some larger issues it is realistic to have 2,3, or more developers working on a task but other tasks cannot be accomplished by developers working in parallel.

      Additionally, some teams can work this way, some cannot. I'd prefer not to create a Portfolio Plan for each team only so I can configure different scheduling.

      While it could be argued that a large task could be broken down into smaller tasks and set the "Maximum assignees per story" to 1 it's not always that easy when the requirements are not yet detailed to break down and/or you simply need to project across multiple future releases. This allows us to justify hiring early enough to onboard, and get up to speed in time.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              benfer_adam Adam Benfer
              Votes:
              9 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated: