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

Ability to pick Compass components fields within Jira Service Management project

XMLWordPrintable

    • 22
    • 15
    • 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.

      Problem

      Compass can be synchronized with JSM Services. However, the Compass component only allows the selection of associated services and not the related components listed under a service.

      Suggested Solution

      • Components are not equivalent to services and should not be treated as such.
      • The absence of the "Compass Components" field in Jira products is causing inconvenience and should be reinstated.
      • There is a need for a one-to-many relationship from Service to Compass Component(s) instead of the current 1:1 requirement.
      • The redesign requirements of 1:1 relationships in JSM Service Management tickets are deemed unnecessary and counterproductive.

      Workaround

      • Create Service Type components in Compass for the JSM Services and instruct the team to only use the higher level ones. maybe with a specific naming convention.
      • Use the Capability component type to match with the JSM Services and maintain it manually; ignore the synced services (not ideal)

              ksilver Katie Silver (Inactive)
              374f558c9a00 Gerry Martinez
              Votes:
              11 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: