Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-89792

Support relative time estimations

XMLWordPrintable

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

      As where JIRA Agile already supports switching between Story Points and Estimated hours, this should too.

            [JRACLOUD-89792] Support relative time estimations

            Martin Suntinger added a comment -

            All, thank you for voting and commenting on this issue - we're excited to announce that with JIRA Portfolio 1.7 we have finally added support for story point estimation and progress tracking: https://confluence.atlassian.com/display/JIRAPortfolio/JIRA+Portfolio+1.7+Release+Notes - we're looking forward to receiving your feedback and comments to further improve the add-on now that we've established the basic functionality for working with story points!

            Martin Suntinger
            Product Manager for JIRA Portfolio

            Martin Suntinger added a comment - All, thank you for voting and commenting on this issue - we're excited to announce that with JIRA Portfolio 1.7 we have finally added support for story point estimation and progress tracking: https://confluence.atlassian.com/display/JIRAPortfolio/JIRA+Portfolio+1.7+Release+Notes - we're looking forward to receiving your feedback and comments to further improve the add-on now that we've established the basic functionality for working with story points! Martin Suntinger Product Manager for JIRA Portfolio

            Chris Nicosia added a comment -

            Fully agree I love the concept but I don't want to invest anytime into even evaluating unless story points are included

            Chris Nicosia added a comment - Fully agree I love the concept but I don't want to invest anytime into even evaluating unless story points are included

            intersol_old added a comment -

            Here at Citrix, the lack of Story Points support was enough to block further investigation of the JPO plugin.

            intersol_old added a comment - Here at Citrix, the lack of Story Points support was enough to block further investigation of the JPO plugin.

            Russell Smith added a comment -

            I voted for this and wanted to add some detail from my perspective:

            • Story Point estimations should be unique to each Team. If a user changes the Team on a Story that already has a Story Point Estimate, they should be made aware that the Estimate should be revised.
            • There should be an option to enter the Velocity for each Team (and/or have it imported from JIRA Agile). This will enable JIRA Portfolio to calculate the stories to include in forthcoming sprints.
            • This can (and should) apply to both Scrum and Kanban teams.

            Russell Smith added a comment - I voted for this and wanted to add some detail from my perspective: Story Point estimations should be unique to each Team. If a user changes the Team on a Story that already has a Story Point Estimate, they should be made aware that the Estimate should be revised. There should be an option to enter the Velocity for each Team (and/or have it imported from JIRA Agile). This will enable JIRA Portfolio to calculate the stories to include in forthcoming sprints. This can (and should) apply to both Scrum and Kanban teams.

              Unassigned Unassigned
              5b8fbcaff108 Patrick van der Rijst
              Votes:
              27 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: