Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-19563

Support Per Issue/Subtask "Maximum assignees per story"

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? 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

              Unassigned Unassigned
              5323dbec9f33 Adam
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: