Portfolio specific configuration

Go to Administration > Settings > Platform. Click the Portfolio Specific Configuration button on one of the tabs and select the portfolio you need. This allows setting each portfolio in a different way.

• Max Task Size In Hours: Controls the maximum size of a task. Lower task sizes encourage better estimates.
• Points System: Controls which scheme of numbers is available to the team when voting on the size of a story. This also controls how WSJF is calculated (if applicable).
• Velocity Range (+ or -): Controls a built-in metric to show teams what the desired velocity variability should be to drive better predictability.
• Manage Products: Turns on or turns off the product option when creating features. This is necessary for organizations that need distinct programs and distinct products. Many organizations can align products and programs, which makes this setting unnecessary.
• Hide Feature Sorting: Controls visibility of the feature sort in the program backlog. The epic and stand-alone feature sort is always available. Depending on your process, you may or may not want to sort features within the epics as well.
• Agile Framework: Adds a specific language, estimation methods, and menus for known scaled agile frameworks. If you do not use a specific framework, select the hybrid framework.
• Use WSJF With Other Estimation Techniques: Allows you to use WSJF for prioritization along with another estimation system for the actual estimate. It applies to the backlog, forecast, and estimation pages. To enable this option, please contact Jira Align support.
• Estimation System: Controls what method is used to estimate work for epics, capabilities, and features. Selection of Points reveals the Display Estimates In drop-down menu to choose Fibonacci, Open Text Field, or Power of 2.
• Display Estimates In: Sets the estimation method for epics, capabilities, and features such as an open text field, Fibonacci numbers, or power of 2. This option appears only if you select Points as the estimation type from the Estimation System drop-down menu.
• Costing Method: Controls if cost is calculated by a PI blended rate or by an individual cost center applicable for each resource.
• Enable Capabilities: Turns on or turns off the visibility of capabilities for specific portfolios. Enabling capabilities puts a layer between epics and features. An epic is associated with capabilities and capabilities are associated with features. The direct epic and feature association is no longer possible. Once capabilities are enabled, they cannot be turned off.
• Capitalization Method: Controls if epics are capitalized at the task or story level for each feature. The option selected here will override the option selected in the Portfolio settings.
• Scorecards: Controls if epics and capabilities can be measured using scorecards. Turns off the Value tab on the epic and capability details slide-out panel if both Scorecards and Value Engineering is set to No.
• Value Engineering: Controls if epics and capabilities can be measured using value engineering. Turns off the Value tab on the epic and capability details slide-out panel if both Scorecards and Value Engineering is set to No.
• Progress Bar Status: Controls how your progress bars will be displayed throughout Jira Align. To enable this option, please contact Jira Align support or SA teams. There are three ways to show the progress bar status:
  
  • Progress by Story Points is progress by effort points on an item.
  • Progress by Count is progress by child count. If you look at features, for example, it will show the count of stories for them (6 out of 10 stories completed).
  • Progress by State is progress by child state. For example, a feature has 10 stories: 6 are accepted, 2 are in progress, and 2 are not started. The progress bar will be 6/10 = 60% complete for the feature.
• Enable Progress to State Mapping: Controls if progress bars for stories that don’t have tasks will reflect the story state. When this setting is set to Yes and a story is accepted, the progress bar fills completely. This setting is primarily intended for teams not using tasks.
• Progress View Type: Controls whether you want to see progress dials or progress bars.
• Progress Alert Threshold: Top percentages are time elapsed, while the bottom percentages are percent complete of the work items. Percentages can be less than or equal to values. For example, you have a progress bar, the vertical line shows where you are as of today; it shows the time elapsed. If you use story points, the green bar shows all story points completed (accepted), and the gray bar shows all story points that are in progress. If the time elapsed is at 70%, and the completed work did not pass 50%, then the green bar will turn red (late). This way, you can see that something is wrong with this item in red because based on the thresholds it should be over 50% by now. If the completed work goes to 62%, the bar will turn orange (warning).
• Progress Alert On: Turns on or turns off the progress alert thresholds for the selected items in such places as, for example, work items' grids, Team Room, Program Room, and Portfolio Room. When enabled, you will see the Late (for example as depicted on the image, the time elapsed is at almost 50%, and the completed work did not pass even 5%) or Warning (for example, the time elapsed is at 70%, and the completed work is at 62%) alerts when pointing to the progress bars on the selected items.