-
Suggestion
-
Resolution: Unresolved
-
None
User Problem
Our Jira and Atlassian Profiles are configured to a non-english language, and our workflow statuses are values like "닫은" or "En cours". We would like to be able to configure our JIRA integration so that when we acknowledge or close an alert, it will update the status of the issue to our desired value and not "In Progress" which does not exist in our non-english workflow. We also would like to create custom statuses and transition to them instead of "In Progress"
Suggested Solutions
Add more functionality to the section "For alerts created by Jira:" and improve it so that when an alert is acknowledged or close we can supply the name of the Status Code we wish the JIRA issue to be transitioned to. It should allow us to provide this text in any language. We shouldn't have to just choose "In Progress" or "Closed".
We should also see an error in the activity log for an alert if the transition hasn't occurred because we could not match that Status Text for an alert. This would allow us to remedy any spelling/copy-paste mistakes that could affect the match.
Current Workarounds
Currently, we have to have workflows with the Status of "In Progress" or "Closed" (in English) and ensure that the user which we connect the JIRA and Opsgenie instances has their Atlassian Account profile set to use "English".
Another possible workaround to this limitation is to add a comment to the ticket when the alert is knowledge. The comment could be a string like transition the issue to X. On the Jira side, create an automation rule that should scan the comment and if the comment matches the string that was passed on from the Opsgenie then the automation rule can transition the issue to the desired status - Reference knowledge base article: JSM/OpsGenie: Move Jira Service Management issue to a certain status other than Done when corresponding OpsGenie alert is acknowledged or closed
- is related to
-
- Gathering Interest
[OPSGENIE-157] I would like to Acknowledge or Close an alert and have it transition my JIRA issue to a Custom Status in my Workflow
| Remote Link | New: This issue links to "Page (Confluence)" [ 924354 ] |
| Description |
Original:
h3. User Problem
Our Jira and Atlassian Profiles are configured to a non-english language, and our workflow statuses are values like "닫은" or "En cours". We would like to be able to configure our JIRA integration so that when we acknowledge or close an alert, it will update the status of the issue to our desired value and not "In Progress" which does not exist in our non-english workflow. We also would like to create custom statuses and transition to them instead of "In Progress" h3. Suggested Solutions Add more functionality to the section "For alerts created by Jira:" and improve it so that when an alert is acknowledged or close we can supply the name of the Status Code we wish the JIRA issue to be transitioned to. It should allow us to provide this text in any language. We shouldn't have to just choose "In Progress" or "Closed". We should also see an error in the activity log for an alert if the transition hasn't occurred because we could not match that Status Text for an alert. This would allow us to remedy any spelling/copy-paste mistakes that could affect the match. h3. Current Workarounds Currently, we have to have workflows with the Status of "In Progress" or "Closed" (in English) and ensure that the user which we connect the JIRA and Opsgenie instances has their Atlassian Account profile set to use "English". Another possible workaround to this limitation is to add a comment to the ticket when the alert is knowledge. The comment could be a string like *transition the issue to X*. On the Jira side, create an automation rule that should scan the comment and if the comment matches the string that was passed on from the Opsgenie then the automation rule can transition the issue to the desired status. |
New:
h3. User Problem
Our Jira and Atlassian Profiles are configured to a non-english language, and our workflow statuses are values like "닫은" or "En cours". We would like to be able to configure our JIRA integration so that when we acknowledge or close an alert, it will update the status of the issue to our desired value and not "In Progress" which does not exist in our non-english workflow. We also would like to create custom statuses and transition to them instead of "In Progress" h3. Suggested Solutions Add more functionality to the section "For alerts created by Jira:" and improve it so that when an alert is acknowledged or close we can supply the name of the Status Code we wish the JIRA issue to be transitioned to. It should allow us to provide this text in any language. We shouldn't have to just choose "In Progress" or "Closed". We should also see an error in the activity log for an alert if the transition hasn't occurred because we could not match that Status Text for an alert. This would allow us to remedy any spelling/copy-paste mistakes that could affect the match. h3. Current Workarounds Currently, we have to have workflows with the Status of "In Progress" or "Closed" (in English) and ensure that the user which we connect the JIRA and Opsgenie instances has their Atlassian Account profile set to use "English". Another possible workaround to this limitation is to add a comment to the ticket when the alert is knowledge. The comment could be a string like {*}transition the issue to X{*}. On the Jira side, create an automation rule that should scan the comment and if the comment matches the string that was passed on from the Opsgenie then the automation rule can transition the issue to the desired status - Reference knowledge base article: [JSM/OpsGenie: Move Jira Service Management issue to a certain status other than Done when corresponding OpsGenie alert is acknowledged or closed|https://confluence.atlassian.com/jirakb/jsm-opsgenie-move-jira-service-management-issue-to-a-certain-status-other-than-done-when-corresponding-opsgenie-alert-is-acknowledged-or-closed-1252000201.html] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 774078 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 774253 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 705811 ] |
| Link | New: This issue is related to OPSGENIE-521 [ OPSGENIE-521 ] |
| Description |
Original:
h3. User Problem
Our Jira and Atlassian Profiles are configured to a non-english language, and our workflow statuses are values like "닫은" or "En cours". We would like to be able to configure our JIRA integration so that when we acknowledge or close an alert, it will update the status of the issue to our desired value and not "In Progress" which does not exist in our non-english workflow. We also would like to create custom statuses and transition to them instead of "In Progress" h3. Suggested Solutions Add more functionality to the section "For alerts created by Jira:" and improve it so that when an alert is acknowledged or close we can supply the name of the Status Code we wish the JIRA issue to be transitioned to. It should allow us to provide this text in any language. We shouldn't have to just choose "In Progress" or "Closed". We should also see an error in the activity log for an alert if the transition hasn't occurred because we could not match that Status Text for an alert. This would allow us to remedy any spelling/copy-paste mistakes that could affect the match. h3. Current Workarounds Currently, we have to have workflows with the Status of "In Progress" or "Closed" (in English) and ensure that the user which we connect the JIRA and Opsgenie instances has their Atlassian Account profile set to use "English". Another possible workaround to this limitation is to add a comment to the ticket when the alert is knowledge. The comment could be a string like *transition the issue to X*. On the Jira side, create an automation rule that should scan the comment and if the comment matches the string that was passed on from the Opsgenie then the automation role can transition the issue to the desired status. |
New:
h3. User Problem
Our Jira and Atlassian Profiles are configured to a non-english language, and our workflow statuses are values like "닫은" or "En cours". We would like to be able to configure our JIRA integration so that when we acknowledge or close an alert, it will update the status of the issue to our desired value and not "In Progress" which does not exist in our non-english workflow. We also would like to create custom statuses and transition to them instead of "In Progress" h3. Suggested Solutions Add more functionality to the section "For alerts created by Jira:" and improve it so that when an alert is acknowledged or close we can supply the name of the Status Code we wish the JIRA issue to be transitioned to. It should allow us to provide this text in any language. We shouldn't have to just choose "In Progress" or "Closed". We should also see an error in the activity log for an alert if the transition hasn't occurred because we could not match that Status Text for an alert. This would allow us to remedy any spelling/copy-paste mistakes that could affect the match. h3. Current Workarounds Currently, we have to have workflows with the Status of "In Progress" or "Closed" (in English) and ensure that the user which we connect the JIRA and Opsgenie instances has their Atlassian Account profile set to use "English". Another possible workaround to this limitation is to add a comment to the ticket when the alert is knowledge. The comment could be a string like *transition the issue to X*. On the Jira side, create an automation rule that should scan the comment and if the comment matches the string that was passed on from the Opsgenie then the automation rule can transition the issue to the desired status. |
| Description |
Original:
h3. User Problem
Our Jira and Atlassian Profiles are configured to a non-english language, and our workflow statuses are values like "닫은" or "En cours". We would like to be able to configure our JIRA integration so that when we acknowledge or close an alert, it will update the status of the issue to our desired value and not "In Progress" which does not exist in our non-english workflow. We also would like to create custom statuses and transition to them instead of "In Progress" h3. Suggested Solutions Add more functionality to the section "For alerts created by Jira:" and improve it so that when an alert is acknowledged or close we can supply the name of the Status Code we wish the JIRA issue to be transitioned to. It should allow us to provide this text in any language. We shouldn't have to just choose "In Progress" or "Closed". We should also see an error in the activity log for an alert if the transition hasn't occurred because we could not match that Status Text for an alert. This would allow us to remedy any spelling/copy-paste mistakes that could affect the match. h3. Current Workarounds Currently, we have to have workflows with the Status of "In Progress" or "Closed" (in English) and ensure that the user which we connect the JIRA and Opsgenie instances has their Atlassian Account profile set to use "English". |
New:
h3. User Problem
Our Jira and Atlassian Profiles are configured to a non-english language, and our workflow statuses are values like "닫은" or "En cours". We would like to be able to configure our JIRA integration so that when we acknowledge or close an alert, it will update the status of the issue to our desired value and not "In Progress" which does not exist in our non-english workflow. We also would like to create custom statuses and transition to them instead of "In Progress" h3. Suggested Solutions Add more functionality to the section "For alerts created by Jira:" and improve it so that when an alert is acknowledged or close we can supply the name of the Status Code we wish the JIRA issue to be transitioned to. It should allow us to provide this text in any language. We shouldn't have to just choose "In Progress" or "Closed". We should also see an error in the activity log for an alert if the transition hasn't occurred because we could not match that Status Text for an alert. This would allow us to remedy any spelling/copy-paste mistakes that could affect the match. h3. Current Workarounds Currently, we have to have workflows with the Status of "In Progress" or "Closed" (in English) and ensure that the user which we connect the JIRA and Opsgenie instances has their Atlassian Account profile set to use "English". Another possible workaround to this limitation is to add a comment to the ticket when the alert is knowledge. The comment could be a string like *transition the issue to X*. On the Jira side, create an automation rule that should scan the comment and if the comment matches the string that was passed on from the Opsgenie then the automation role can transition the issue to the desired status. |
| Summary | Original: I would like to Acknlowedge or Close an alert and have it transition my JIRA issue to a Custom Status in my Workflow | New: I would like to Acknowledge or Close an alert and have it transition my JIRA issue to a Custom Status in my Workflow |
| Description |
Original:
h3. User Problem
Our Jira and Atlassian Profiles are configured to a non-english language, and our workflow statuses are values like "닫은" or "En cours". We would like to be able to configure our JIRA integration so that when we acknowledge or close an alert, it will update the status of the issue to our desired value and not "In Progress" which does not exist in our non-english workflow. We also would like to create custom statuses and transition to them instead of "In Progress" h3. Suggested Solutions Add more functionality to the section "For alerts created by Jira:" and improve it so that when an alert is acknowledged or close we can supply the name of the Status Code we wish the JIRA issue to be transitioned to. It should allow us to provide this text in any language. We shouldn't have to just choose "In Progress" or "Closed". We should also see an error in the activity log for an alert if the transition hasn't occurred because we could not match that Status Text for an alert. This would allow us to remedy any spelling/copy-paste mistakes that could affect the match. h3. Current Workarounds Currently, we have to workflows with the Status of "In Progress" or "Closed" (in English) and ensure that the user which we connect the JIRA and Opsgenie instances has their Atlassian Account profile set to use "English". |
New:
h3. User Problem
Our Jira and Atlassian Profiles are configured to a non-english language, and our workflow statuses are values like "닫은" or "En cours". We would like to be able to configure our JIRA integration so that when we acknowledge or close an alert, it will update the status of the issue to our desired value and not "In Progress" which does not exist in our non-english workflow. We also would like to create custom statuses and transition to them instead of "In Progress" h3. Suggested Solutions Add more functionality to the section "For alerts created by Jira:" and improve it so that when an alert is acknowledged or close we can supply the name of the Status Code we wish the JIRA issue to be transitioned to. It should allow us to provide this text in any language. We shouldn't have to just choose "In Progress" or "Closed". We should also see an error in the activity log for an alert if the transition hasn't occurred because we could not match that Status Text for an alert. This would allow us to remedy any spelling/copy-paste mistakes that could affect the match. h3. Current Workarounds Currently, we have to have workflows with the Status of "In Progress" or "Closed" (in English) and ensure that the user which we connect the JIRA and Opsgenie instances has their Atlassian Account profile set to use "English". |