Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-1607

[JIRAALIGN-1607] Portfolio Room - the name of the label intended for PI budget is confusing

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 10.74
    • 10.71, 10.72
    • None
    • Severity 3 - Minor
    • A-Team - SCORP 5

    Description

      Issue Summary

      The budget numbers displayed beside of the program increment in the Portfolio room aren't very obvious in what they represent. The budget numbers beside the PI represent the budget set aside for that Program Increment. Many users confuse this number for the total budget in the Epics listed below it. See attached screenshot:

      After discussing this with Product Management and Engineering, this is actually working as designed. Product recommended, however, that we change the name of the "Budget" column circled in the screenshot above to "PI Budget" in order to help avoid confusion.

      Steps to Reproduce

      Log in to https://alignsupport.agilecraft.com

      Select Performance Portfolio 1 in Tier 1 portfolio

      Navigate to the Portfolios Room

      When in the room, click the "Financials" button.

      Scroll down until you see "Performance PI 3" in the center of the room - The status of the PI should be "In Progress"

      Expand the PI and note there are two Epics with a total budget of $140,000.

      Note just above these Epics there are 3 columns: Budget, Estimate, Actual. The Budget column shows $0.

      Expected Results

      The Budget column header should be renamed to something clearer, such as "PI Budget", since the budget number reported on the line with the name of the PI isn't the sum of the epics. It is the value that's put onto the PI directly.

      Actual Results

      The column is currently named "Budget", which leads users to think that the monetary value should be the sum of all Epics' budgets, when that is not what is intended.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Issue Links

          Activity

            People

              kbyrd@atlassian.com Kyle Byrd (Inactive)
              kbaxley Kent Baxley
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync