-
Bug
-
Resolution: Fixed
-
Low
-
None
-
1
-
Severity 2 - Major
-
No
Issue Summary
If a portfolio is set up to use points for estimating, we only get null values in both the "Estimate Float Value" and the "Estimate Integer Value" for program estimates.
Steps to Reproduce
Support used the following steps to reproduce :
- Pick an epic that has a forecast
- This portfolio should use "Team Weeks" in a portfolio-specific setting, set it to Points
Conversion of 2 Team Weeks = 1.2 Story points, seems in the UI it's being rounded down to 0 - After the data is synced to EI, shows Program estimates as null
- Reverting the Portfolio-specific settings back to Team Weeks restores the numbers in JA to the original
- EI shows the estimate in float and int again
Expected Results
When the "Estimation system" is using Points, it should not show the program estimate as NULL in EI.
Actual Results
- EI shows Program Increment and Program estimates as null
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- blocks
-
PS-180164 You do not have permission to view this issue
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JIRAALIGN-8108] When the Estimate System for a Portfolio is set up to use Points, it shows incorrect data in Enterprise Insights
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Review [ 10051 ] | New: Closed [ 6 ] |
| Fix Version/s | New: 11.9.0 [ 110346 ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10051 ] |
| Support reference count | New: 1 |
| Attachment | New: image-2025-03-21-14-02-38-946.png [ 490818 ] |
| Description |
Original:
h3. Issue Summary
If a portfolio is set up to use points for estimating, we only get null values in both the "Estimate Float Value" and the "Estimate Integer Value" for program estimates. h3. Steps to Reproduce * Pick an epic that has a forecast * This portfolio should use "Team Weeks" in a portfolio-specific setting, set it to Points Conversion of 2 Team Weeks = 1.2 Story points, seems in the UI it's being rounded down to 0 * After the data is synced to EI, shows Program estimates as null * Reverting the Portfolio-specific settings back to Team Weeks restores the numbers in JA to the original * EI shows the estimate in float and int again h3. Expected Results Changing the "Estimation system" should not show the program estimate as NULL in EI. h3. Actual Results * EI shows Program Increment and Program estimates as null h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
If a portfolio is set up to use points for estimating, we only get null values in both the "Estimate Float Value" and the "Estimate Integer Value" for program estimates. h3. Steps to Reproduce Support used the following steps to reproduce : * Pick an epic that has a forecast * This portfolio should use "Team Weeks" in a portfolio-specific setting, set it to Points Conversion of 2 Team Weeks = 1.2 Story points, seems in the UI it's being rounded down to 0 * After the data is synced to EI, shows Program estimates as null * Reverting the Portfolio-specific settings back to Team Weeks restores the numbers in JA to the original * EI shows the estimate in float and int again h3. Expected Results When the "Estimation system" is using Points, it should not show the program estimate as NULL in EI. h3. Actual Results * EI shows Program Increment and Program estimates as null h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Summary | Original: Changing the Estimate System for a Portfolio shows incorrect data in Enterprise Insights | New: When the Estimate System for a Portfolio is set up to use Points, it shows incorrect data in Enterprise Insights |
| Status | Original: Needs Triage [ 10030 ] | New: In Progress [ 3 ] |
| Labels | New: bulldog |
| Remote Link | New: This issue links to "PS-180164 (Atlassian Support System)" [ 999641 ] |