Add Root Cause to Linked Jira Tickets
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Problem Statement
What I would really love to see is the AI used to help create better tickets in Jira. Right now when I have Sentry create a Jira ticket it usually just dumps the stack trace into the description, but if the AI could use the root cause that it found to write up a meaningful description for the Jira ticket that would be amazing
### Solution Brainstorm
The data already seems to be there just a mtter of adding that to the linked Jira ticket.
### Product Area
Issues
Contributor guide
Research direction
The issue names the Jira-linking workflow and the Issues product area, but provides no file, test, or entry point. Begin by locating the existing Sentry-to-Jira ticket creation path and how the AI root-cause result is represented. Done means linked Jira tickets use that root cause in a meaningful description, with coverage for the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100