Dashboard gadget uses incorrect JQL after updating Terminology

XMLWordPrintable

    • 8.22
    • 1
    • Severity 3 - Minor

      Problem

      In Jira Software Data Center 8.22.3 after updating the Terminology for Sprint and Sprints, the JQL in a Dashboard gadget will no longer produce results in the Search Issues page because it requires that the original term be used when performing an advanced search.

      According to our Configuring terminology documentation, this is due to the following expected behavior:

      Advanced search uses the original names of “sprint,” “epic,” and the epic-related fields

      The Terminology feature enables the changes to the term “sprint” and to the term “epic” as the name of the issue type. Also, the new term for “epic” is applied to the names of the epic-related fields: Epic Name, Epic Color, Epic Status, and Epic Link.

      As a result, you’ll see the new terms everywhere in the output: on boards, in issue screens, reports, and basic search filters.
      But the input in API queries or advanced search will still require the original terms for “sprint”, “epic”, and the epic-related fields.

      However, this also causes issues for users who still want to use their Dashboard gadgets but the JQL now uses an incorrect search term.

      Environment

      Jira Software Data Center 8.22.3

      Steps to Reproduce

      1. Create Dashboard
      2. Add Two Dimensional Filter Statistics gadget
      3. Set X axis as Status and Y axis as Sprint
      4. Create Search Filter similar to this:
        1. project = SCRUM AND issuetype = Story AND Sprint in openSprints()
      5. Navigate to Jira Administration > Terminology
      6. Rename "Sprint" and "Sprints" to "Iteration" and "Iterations"
      7. Click any value that is not a total in the gadget and confirm issue occurs.

      Expected Results

      Search Issues page should have the correct JQL used and should provide results like so:

      Actual Results

      JQL does not return the expected results and instead, displays the following error message:

      Workaround

      None at the moment.

      Notes

              Assignee:
              Sławomir Zaraziński
              Reporter:
              Adrian Castillo
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: