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

Update logic of "earliestUnreleasedVersion()" to use earliest date

XMLWordPrintable

    • 5

    • 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 Cloud. Using JIRA Server? See the corresponding suggestion.

      This is a follow on from JRA-1357.

      Currently there is the ability to filter by the issues assigned to the next version by using the earliestUnreleasedVersion() logic. This pulls from the oldest unreleased version. Is there anyway to create the logic for this to use the release date field so that it filters by the version that has the earliest release date?

            [JRACLOUD-41739] Update logic of "earliestUnreleasedVersion()" to use earliest date

            Craeg Strong added a comment - - edited

            Ideally I would love to see a flexible approach, since it is not mandatory to add dates to a release.   Not requiring dates makes sense, since sometimes we know there will be a future release before we actually know the exact dates for the release.   So in many cases the list of future releases may have some combination of some releases with dates and some releases without dates.   

            I believe the behavior that most users would expect would be the following: earliestUnreleasedVersion() should return the release with the earliest date, if any unreleased version has a date.  If none of the unreleased versions has any date, it should use the first-in-list logic that is in place today.  

            I believe this change represents a relatively small amount of work, and it would prevent the kind of strange behavior we have today where just by reordering releases some dashboard somewhere else in the system could show incorrect results.

             

            Craeg Strong added a comment - - edited Ideally I would love to see a flexible approach, since it is not mandatory to add dates to a release.   Not requiring dates makes sense, since sometimes we know there will be a future release before we actually know the exact dates for the release.   So in many cases the list of future releases may have some combination of some releases with dates and some releases without dates.    I believe the behavior that most users would expect would be the following: earliestUnreleasedVersion() should return the release with the earliest date, if any unreleased version has a date.  If none of the unreleased versions has any date, it should use the first-in-list logic that is in place today.   I believe this change represents a relatively small amount of work, and it would prevent the kind of strange behavior we have today where just by reordering releases some dashboard somewhere else in the system could show incorrect results.  

              Unassigned Unassigned
              192e2d9a424b Mike Low
              Votes:
              13 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: