DevOps Automation: "Next unreleased version" always takes the release at very bottom of the list and not actually the next release by date

XMLWordPrintable

    • 3
    • Minor
    • 1

      Issue Summary

      The action to update the FixVersion field to the “next unreleased version” always takes the release at the very bottom of the list and not actually the next release by date.

      Steps to Reproduce

      1. Create an automation rule to edit an issue
      2. Select the field "FixVersions" to be edited
      3. Choose "Next unreleased version" 

      Expected Results

      This should set the FixVersion of the issue considering the next available release date.

      Actual Results

      • If you have only 1 version - it will be picked
      • If you have more than one version, the release at the very bottom of the list will be picked.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Renato Pereira (Inactive)
            Votes:
            15 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: