Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-2629

JIRA Portfolio Custom Field Name is using the Translation key instead

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Bug Bug
    • Resolution: Tracked Elsewhere
    • Icon: Low Low
    • None
    • None
    • Usability
    • None

      Issue Summary

      JIRA Portfolio 3.6.0 in JIRA 8.2 custom fields name is on its translation key like below:

      • rm.jpo.plan.common.baselineEnd
      • rm.jpo.plan.common.baselineStart

      Environment

      JIRA 8.2 (Portflio 3.6)

      Steps to Reproduce

      1. Install JIRA 8.2 with JIRA Portfolio 3.6
      2. Navigate to JIRA Administration > Issues > Custom Fields
      3. Search for the field "Target"

      Expected Results

      "Target End" and "Target Start" should be shown

      Actual Results

      Nothing will be shown because the name is set to the translation key. Searching "rm" will show the following fields:

      Notes

      The issue is caused by a bug affecting JIRA Core which is the platform where Portfolio is installed.

      Workaround

      -

          Form Name

            [JPOSERVER-2629] JIRA Portfolio Custom Field Name is using the Translation key instead

            This bug is caused by Jira Core and the fix to the bug and a task fixing broken installation is available in Jira 8.3.1. See JRASERVER-69388 for details.

            Maciej Swinarski (Inactive) added a comment - This bug is caused by Jira Core and the fix to the bug and a task fixing broken installation is available in Jira 8.3.1. See JRASERVER-69388 for details.

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: