Add ability to customize how Sentry creates the task in Jira

[ilyasgaraev]

Problem Statement

Sentry allows automatically create a Jira issue in the alert and customize Jira issue settings. Unfortunately, now it's not possible to set fields dynamically and set Sentry error's attributes to the Jira task. For example, our team wants to see the [Sentry] prefix in the title if the task is automatically created by Sentry. Or set the error details and link to the error to the custom field.

Solution Brainstorm

It would be great to introduce the dynamic Sentry error's variables to allow dynamically set values in the Jira integration. Example:

Sentry error

Title: ActionView::Template::Error Description: undefined method `name' for nil:NilClass (ActionView::Template::Error) Link: https://example.sentry.io/issues/123/

Jira task settings

Title: [Sentry] ${sentry.title} Custom field: ${sentry.description} Description: Please follow this link to see the error details: ${sentry.link}

Jira task result

Title: [Sentry] ActionView::Template::Error Custom field: undefined method `name' for nil:NilClass (ActionView::Template::Error) Description: Please follow this link to see the error details: https://example.sentry.io/issues/123/

Product Area

Alerts

[getsantry[bot]]

Assigning to @getsentry/support for routing, due by Wednesday, May 10th at 5:00 pm (sfo). ⏲️

[getsantry[bot]]

Routing to @getsentry/product-owners-settings-integrations for triage, due by Thursday, May 11th at 5:00 pm (sfo). ⏲️

[Dhrumil-Sentry]

Hi @ilyasgaraev thanks a lot for the feedback, is there any other field that you'd also like to see be copied over to Jira?

[ilyasgaraev]

Hi @Dhrumil-Sentry!

To cover our current requirements the title, description, and link fields are more than enough. But for the future (MVP+), it might be useful to have tags as separate variables (for example: ${sentry.tags.browser} or ${sentry.tags.release}).

[StevenStampsMGMRI]

There are 2 types of modification we would like to be able to make to the generated ticket:

• add arbitrary text to the default Description (another section header and blank line)
• add our Definition of Done checklist (a dynamic checklist plugin)

[Dhrumil-Sentry]

Hi @StevenStampsMGMRI thanks for the feedback! - Is there any particular information from the Sentry issue that you'd like to see added as well?

What kind of information would you like to add to the default description?

[StevenStampsMGMRI]

Just need to add 2 more bold section headings to the Description after "Confluence pages":

• Triage
• Disposition

Steven

---

From: Dhrumil @.> Sent: Thursday, May 11, 2023 1:57 PM To: getsentry/sentry @.> Cc: Stamps, Steven @.>; Mention @.> Subject: [External] Re: [getsentry/sentry] Add ability to customize how Sentry creates the task in Jira (Issue #48851)

Hi @StevenStampsMGMRIhttps://github.com/StevenStampsMGMRI thanks for the feedback! - Is there any particular information from the Sentry issue that you'd like to see added as well?

What kind of information would you like to add to the default description?

— Reply to this email directly, view it on GitHubhttps://github.com/getsentry/sentry/issues/48851#issuecomment-1544444142, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2L6YJJR5OCFLI3V6YFIOSLXFUSBLANCNFSM6AAAAAAX4MXUUU. You are receiving this because you were mentioned.Message ID: @.***>

[tomas-vojvoda]

Hello,

We are interested in being able to modify the description of the automatically created Jira ticket as well. At the moment the integration adds "Sentry issue details" into the Description field and those only contain Name and two links back to Sentry,.. I'd need it to contain some of the useful info I see in Sentry ticket.

Example added - all I see in the Jira ticket Description is useless, because I have that in other fields.

Specificaly now looking for the option to replace "Issue Details" in linked Jira ticket with "User Feedback" from Sentry issue.

[daywhirls]

+1 to this feature request. We are very interested in being able to customize these fields with a template, specifically the ticket description. As @tomas-vojvoda mentioned, the current information populated in the ticket description is not super helpful for our use-case, and it is tiresome to manually modify the ticket details each time.

[kddsultan]

+1 for description template support. Thats probably a must have, IMO otherwise current integration for at least creates link to Sentry

[a-gerhard]

To add here: It would be nice to put the JIRA issue link into a custom field instead of the description. JIRA is very customizable when it comes to fields on tickets, and I think that different teams have very different fields on their JIRA tickets. It would generally be nice to have a dynamic mapping of any Sentry Issue information to any JIRA fields.

It would also be nice to be able to populate some fields with default values, because coming from sentry, there are some specifics which are almost always the same. Examples:

• Reporter (assign to self)
• Ticket type (always a bug report, not something related to feature requests)

[tomas-vojvoda]

It would also be nice to be able to populate some fields with default values, because coming from sentry, there are some specifics which are almost always the same. Examples:

• Reporter (assign to self)
• Ticket type (always a bug report, not something related to feature requests)

Hello Alissa - I believe you can handle this part with Jira automation easily. Just a note. Cheers.