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

Make scheduling criteria and automatic assignment of teams optional

XMLWordPrintable

    • 0
    • 1

    • 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.

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

      Motivation

      As a Product Owner I want to have more control over the Roadmap generated by JIRA Portfolio 2.0 to achieve the most useful and informative results for my stakeholders.

      Background

      The idea of generating data driven roadmaps via JIRA Portfolio 2.0 is awesome. Unfortunately the scheduler behaves "too smart" from time to time. Especially when it decides to prepone tickets that were prioritized lower for the sake of filling up sprints and to optimize capacity workload across sprints. The workaround of using dependencies is troublesome since you might end up chaining a lot of tickets to prevent JIRA Portfolio 2.0 to prepone some other tickets which is even lower in the backlog.

      Also the automatic assignment of Teams to a Story or Epic is more often a burden than of help.

      It's ok, that these functionalities are there. But I would love them to be optional and use only the criteria that I need.

              Unassigned Unassigned
              a70453d5fe06 Salah
              Votes:
              8 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: