-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
3
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Problem Definition
Currently, Portfolio calculates whether a release is overbooked or not by using the issues scheduled for that sprint. As such, when a release is done within a sprint period, the release shows as Overbooked as issues are scheduled for the whole period of the sprint.
Suggested Solution
Allow Releases to be re-calculated when it is done within a sprint period.
Why this is important
When releases are done within a sprint, users would be able to see that the Release is not overbooked when it is calculated based on capacity.
- relates to
-
JRACLOUD-89046 Re-calculate releases using capacity if it falls within a sprint
- Closed
Re-calculate releases using capacity if it falls within a sprint
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
0
-
3
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Problem Definition
Currently, Portfolio calculates whether a release is overbooked or not by using the issues scheduled for that sprint. As such, when a release is done within a sprint period, the release shows as Overbooked as issues are scheduled for the whole period of the sprint.
Suggested Solution
Allow Releases to be re-calculated when it is done within a sprint period.
Why this is important
When releases are done within a sprint, users would be able to see that the Release is not overbooked when it is calculated based on capacity.
- relates to
-
JRACLOUD-89046 Re-calculate releases using capacity if it falls within a sprint
- Closed