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

Allow maximum assignees per epic

    XMLWordPrintable

Details

    • Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • None
    • None
    • None
    • 0
    • 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

      At the moment Portfolio assigns the whole team to each epic, assuming they will be completed one-by-one as a team. 

      Whilst I can understand some of the reasons behind this, a lot of the time it's completely unrealistic. For example it may only be possible for 2 people to work on an epic at once, and the rest of the team can focus on a different initiative. Also putting a whole team of 5 developers onto an epic with a 10 day estimate and assuming this means it will be completed in 2 days is both wrong (it would probably take longer) and leads to a ridiculous looking roadmap.

      A workaround is to assign specific team members to each epic. However this doesn't work particularly well as it restricts Portfolio's ability to move work around. What if you don't care who does the work, you just know you want to assign 2 developers to this, 3 to that etc.

       

      At the moment it's possible to restrict the number of developers assigned per story. We would like a similar feature, but the ability to put a limit on the number of developers that can be assigned on a per epic basis.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              62543a22077f Matt Dabell
              Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: