-
Type:
Bug
-
Resolution: Timed out
-
Priority:
Low
-
Component/s: Service Registry
-
1
-
Minor
Issue Summary
Customer created services from an external source using GraphQL queries to populate Asset -> Services -> Applications that use the app_ prefix. They are setting service responders through these GraphQL queries.
However, after this process, they are unable to view or modify the responders via the web user interface.
Steps to Reproduce
- Create a service via UI:
- Navigate to: Asset -> Services -> Applications
- Click on the "Create Object" button (top right corner).
- Provide Service details:
- Service Name : test
- Service Type: Application
- Tier: Tier 3
- Owner: <owner>
- Click button "Create Service".
- Verify the service in the JSM project:
- Navigate to JSM project → Services and locate the newly created service from step 1
- Click the three dots in the top right corner → Edit Service.
- Locate the Responders field, add value, and click "Save".
- Now, the responders should be visible in the service details page:
- JSM project>Services
- Same on Asset -> Services -> Applications
- Update the service responders via GraphQL:
- Navigate to Atlassian GraphQL API.
- Execute the following mutation:
graphql mutation updateServiceResponders { updateDevOpsService(input:{ id: "ari:cloud:graph::service/<id>/<id>", revision: "251091486", name: "<>", serviceTier: "<>", properties:[{key:"responders", value: {teams:["ari:cloud:opsgenie:<id>:team/<teamid>"]}}] }) { ... on UpdateDevOpsServicePayload { success errors { ... on MutationError { message } } service { ... on DevOpsService { id revision name description serviceTier { id level } serviceType { key } properties(keys:["responders"]) } } } } }
- Verify the service details after GraphQL update:
-
-
- Check the JSM project → Services details page:
-
-
-
-
- Issue: No responders are displayed.
- Try to edit the service → The "Responders" field is missing.
- Check the Assets → Services → Applications details page:
- Here, the responders are still visible.
-
-
Expected Results
The responders should be updated on the JSM project services field.
Actual Results
The responders are not updated/field is missing.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available