Create Jira tickets directly from Session Replay pages
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Problem Statement
Currently, we can only create Jira tickets from Sentry issues that are automatically detected. However, during review of session replays, we often discover UX problems, unexpected user behaviors, or other issues that don't trigger error events but still need development attention. We need the ability to create and associate Jira tickets directly from session replay pages, even when no error is detected.
### Solution Brainstorm
Add functionality to the Session Replay interface that allows users to:
Create a new Jira ticket directly from the replay page
Include a link to the specific replay in the Jira ticket
Add relevant timestamps from the replay to the Jira ticket description
Associate existing Jira tickets with replays for tracking purposes
This would greatly improve our workflow when identifying issues through replay analysis, especially for checkout flows where we've implemented 50% general session capture and 100% error session capture.
### Product Area
Unknown
Contributor guide
Research direction
No files, tests, or entry points are named. Start by tracing the existing Jira-ticket flow from Sentry issues and the Session Replay page, then define how replay links and timestamps are passed through. Done means users can create new Jira tickets from replays and associate existing tickets with them.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100