Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-15093

Contextual dropdowns - basic search in JSD shows incorrect options when custom field restricted by project context - should only show fields and values from current project

XMLWordPrintable

      NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding bug report.

      Description of problem

      Components drop-down menu should list only target project related items on Create/Clone Issue action

      Custom field has global context and additional context with different options. Additional context is set for JSD project.

      JSD search fields allow custom field to be selected and present options for global context. Does not show options configured in additional context tied to JSD project.

      Reproduced in:

      • Server 3.3.0
      • Cloud v3.3.0-OD-1000.846.0 / JIRA v1000.718.6

      Steps to reproduce

      1. Create JSD project
      2. Create new checkbox custom field with "Global" value, add to JSD project screens.
      3. Create new context for custom field, associate with JSD project. Add value "JSDvalue"
      4. Attempt to add field to JSD project queue, automation, or reports
        • For example, create new queue and in basic "Issues to show" select the new field and try to select value.

      Experienced behavior

      Custom field presents options tied to global context. These are the incorrect options.

      • Does not show options tied to JSD project context.

      Expected behavior

      JSD shows correct values in basic search dropdown.

      • These would be the options set for the context tied to the JSD project.

      Workaround

      Use the advanced search option to configure the report, queue, or automation rule.

      Additional notes

      Request types work properly, showing the options from the project specific context and no options from global context.

      • The portal presents the correct options
      • When hiding field the default option selection shows correct options

       

      Related issues

      • When there are different fields with the same name, one for Next-Gen project and other for Classic project, it's not possible to differentiate them into the drop-down selection in Automation:

              Unassigned Unassigned
              tevans Tim Evans (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: