-
Suggestion
-
Resolution: Unresolved
-
16
-
Issue Summary
Currently, the Responders field is not listed in the Edit issue action in Jira Automation. To update it, you need to use advanced field editing using JSON, following this guide.
The Opsgenie team ID is needed to add Teams as responders, which works. However, in the consolidated JSM Operations, users are unable to access the Opsgenie UI to gather this ID or retrieve it using the Opsgenie API call https://api.opsgenie.com/v2/teams.
Steps to Reproduce
- Create an automation rule following this guide.
- Use Atlassian Team ID in the automation rule.
Expected Results
For consolidated instances be able to use Atlassian Team ID to update the issue responder's field.
Actual Results
A blank responder is added and no one is notified.
Workaround
- Manually add a team as a responder to an incident issue.
- Retrieve all field values for that issue using expand https://<instancename>.atlassian.net/rest/api/2/issue/<issuekey>?expand=names to see the Responders field data and extract the ID.
- Use the extracted ID in the automation rule.
- mentioned in
-
Page Failed to load
[JSDCLOUD-14682] Unable to add Teams as incident responders via automation
Also,
- When adding the 'Team' field to a Request Screen, it shows up as hidden without a way to set a value
- When doing a lookupObject on Services, the Service Owners.id returns a short code such as 344
https://<instancename>.atlassian.net/gateway/api/jsd/escalator/<cloud-id>/api/teams
The above url only seems to be usable from a Browser and not via an Automation Web request using a valid token. The appears to be no other way of obtaining a Team's opsgenie ARI value (programmatically) for updating the "Responders" field, based on a known matching Team name.
2a1be9291630 - This is not really a bug, but rather a feature request. Can we update this to a JAC ticket?
As a substitute for **
https://api.opsgenie.com/v2/teams
You can try the following URL
https://<instancename>.atlassian.net/gateway/api/jsd/escalator/<cloud-id>/api/teams
Hi team,
in fact the workaround is working but it is generating a lot more effort to onboard new projects in our company by that.
Can you please prioritize this and make it possible to work with the team ID of JSM instead of having to grep the OpsGenie ID via API call? How long will this workaround work if you sundown OpsGenie?
Best regards