Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-9290

Issue Detail View configuration should respect custom field configuration context

XMLWordPrintable

    • 0
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Greenhopper allows user to configure custom field in the issue detail view, however all the custom fields in JIRA are shown whether the it's related to the project used in the filter or not.

      For example:

      1. Custom Field B are available to project B only as specified in the field configuration context while Custom Field A are available to project A.
      2. User had a scrum board with project A only.
      3. User want to configure custom field A to the board issue detail view.
      4. However, in the configuration, both Custom Field A and B shown up for selection.

      Use Case:

      • Imagine a JIRA instance has 100 custom fields and some of them are not associated to the correct project.
      • This will generate a serious confusion and painful process on configure the field to the board.
      • Worse case scenario - several fields with same name(some users have such scenario) added to the view. If the wrong field were selected, the value would not shown in the issue detail view.

              Unassigned Unassigned
              yen@atlassian.com TeckEn (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: