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

JIRA Portfolio Custom Field Name is using the Translation key instead

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Low
    • Resolution: Tracked Elsewhere
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Usability
    • Labels:
      None

      Description

      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

      -

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jrahmadiputra Julian (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: