Uploaded image for project: 'Agile Poker Enterprise for JIRA'
  1. Agile Poker Enterprise for JIRA
  2. APJ-801

Agile Poker breaks if Rank field is renamed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Summary

      The Rank field is a Jira Software field that's locked by default. It is, however, possible to unlock this field. Check out this KB: Translating JIRA Agile Custom Fields. After unlocking the field we're able to do pretty much whatever we want. That means, we can rename the field. Not translate, but rename.

      Environment

      • Jira 7.4.3

      Steps to Reproduce

      1. Unlock Rank field using this KB article: Translating JIRA Agile Custom Fields.
      2. Rename the field from Rank to Rang (German version).
      3. Try to start a relative session.

      Expected Results

      Relative session is started.

      Actual Results

      Issues never finish loading and we get a 400 bad request error message in the logs because the field Rank couldn't be found.

      Workaround

      Change the name of the field back to 'Rank' (original) and then use the translate function provided by Jira to translate the field instead of renaming it.

      Notes

      If you keep the original field Rank and just translate it to German (Rang), then everything works as expected. The problem only happens when you rename the field. That's because the name of the field is hardcoded: https://bitbucket.org/spartez/jpp-ng/src/c937a9f9a34558622e34e052f2da85effae0ebf5/pokerng-frontend/src/commons/issues-selector/issueSelectorModule.js?at=master#lines-13.

        Attachments

          Activity

            People

            • Assignee:
              pstefaniak Piotr Stefaniak
              Reporter:
              brosa Bruno Rosa
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: