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

Allow scheduling algorithm to use initiative backlog for prioritization as opposed to epic backlog

    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.

      Summary

      Currently the scheduling algorithm uses the stack-ranking of epics to determine scheduling constraints. If an individual creates an initiative later that supersedes another intiative then they have to manually pull up all the epics in that initiative above the epics in another initiative to reflect this relative initiative prioritzation. It would be very helpful if in the scheduling configuration section if you could designate priority on an initiative basis as opposed to an epic basis.

      Background

      Our organization is very initiative focused and we determine organizational priorities based on the initiatives. We recently had a late initiative come into place that superseded all other initiatives. As we began to build the plan, bucket work into epics and then stories, some of these high priority epics were seemingly started later than expected causing an unrealistic timeline. This caused a lot of manual work to change the epic prioritization to match the initiative priortization.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ba300737d596 Matthew Leggett
              Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: