Uploaded image for project: 'Xray for Jira'
  1. Xray for Jira
  2. XRAY-9542

When changing the name of the Fix version, the system doesn't trigger the recalculation of the requirement status

    XporterXMLWordPrintable

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • Xray DC V7.2.1
    • None
    • Requirement Status
    • None
    • UNCOVERED

    Description

      When changing the name of the Fix version, the system doesn't trigger the recalculation of the requirement status.

      Precondition:

      Manage apps->xray->custom fields

      and enable the configurations for

      Requirement Status Custom Field Version-> Assigned versions 

      Test Run Status Custom Field Version->Earliest Unreleased Version

      Steps to reproduce:

      • Create one version. 'Releases 1.0'
      • Create a story with 'Releases 1.0'
      • Create a test related to the story.
      • Create a test execution with 'Releases 1.0', and the test run result is PASS
      • Check the story requirement is OK
      • Modify the release name from 'Releases 1.0' to 'Releases 1.0-a'
      • Check the story requirement is NOT RUN on 'Releases 1.0-a'

      Expected result:

      • The system should automatically update the requirement status when the release name is changed.

      Currently, to display the correct results, it is necessary to clear all Calculated Custom Field Values under the Xray Integrity Checker, but this process should be automatic.

      Attachments

        Activity

          People

            dpca Diamantino Campos
            pmax Paulo Aleixo
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: