We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-89046

Re-calculate releases using capacity if it falls within a sprint

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Timed out
    • Plans - Timeline
    • None

    • 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.

      NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? 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.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Platform Cloud'
            1. Jira Platform Cloud
            2. JRACLOUD-89046

            Re-calculate releases using capacity if it falls within a sprint

            XMLWordPrintable

              • Icon: Suggestion Suggestion
              • Resolution: Timed out
              • Plans - Timeline
              • None

              • 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.

                NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? 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.

                        Unassigned Unassigned
                        nghanis Nithiyaa Ghanis (Inactive)
                        Votes:
                        4 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            nghanis Nithiyaa Ghanis (Inactive)
                            Votes:
                            4 Vote for this issue
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated:
                              Resolved: