Allow JSM portal dropdown fields to dynamically filter options based on the logged‑in customer’s Jira project membership, and auto‑populate related fields based on that selection.

XMLWordPrintable

    • 1
    • Hide
      1. Per‑user filtered dropdowns on the portal

      On JSM customer portals, allow certain field types (e.g. Select, Assets object, or a dedicated Project picker) to filter options based on the current logged‑in customer, such as:

        • “Only show projects where this user has a specific role or permission”
        • “Only show projects linked to this customer’s organization”
        • Possibly driven by a configurable rule (e.g. group/role, org, Assets relationship).
      1. Portal‑time derived fields

      Allow a second field on the portal (e.g. Project Manager / Solution Architect) to be automatically populated or constrained based on the selected value in the first field (e.g. Project), using a simple mapping or Assets relationship, before submission, so the customer sees the correct value.

      It would be sufficient if admins could configure:

      • A Project field that:
        • Filters to “projects for this requester” according to a defined rule (membership, organization, Assets link, etc.)
      • A dependent field (PM / SA) that:
        • Reads from a mapping or Assets object linked to the selected project.
        • Is either read‑only or auto‑defaulted for the customer.
      Show
      Per‑user filtered dropdowns on the portal On JSM customer portals, allow certain field types (e.g. Select , Assets object , or a dedicated Project picker ) to filter options based on the current logged‑in customer , such as: “Only show projects where this user has a specific role or permission” “Only show projects linked to this customer’s organization” Possibly driven by a configurable rule (e.g. group/role, org, Assets relationship). Portal‑time derived fields Allow a second field on the portal (e.g. Project Manager / Solution Architect ) to be automatically populated or constrained based on the selected value in the first field (e.g. Project ), using a simple mapping or Assets relationship, before submission , so the customer sees the correct value. It would be sufficient if admins could configure: A Project field that: Filters to “projects for this requester” according to a defined rule (membership, organization, Assets link, etc.) A dependent field (PM / SA) that: Reads from a mapping or Assets object linked to the selected project. Is either read‑only or auto‑defaulted for the customer.

      Current State:

      Today, Jira Service Management customer portal fields are static per request type:

      • A dropdown field presents the same list of options to all customers.
      • There is no way to make the options depend on who is logged in or which Jira projects they are associated with.

      Our use case:

      • External users submit a Change Request via the customer portal.
      • Each external user is associated with one or more Jira projects and has a designated Project Manager / Solution Architect for that project.
      • We need the request form to:
        1. Show a Project dropdown that lists only the projects the current requester is associated with in Jira.
        1. When the requester selects a Project, automatically populate a second field (e.g. Project Manager / Solution Architect) based on a predefined mapping.

       

      Proposed Future State:

      NA

      Alternative (e.g. Third Party Plugin):

      NA

              Assignee:
              Unassigned
              Reporter:
              Adithyan A
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: