Missing some updates on channel, with Slack and Jira integrations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Hi. A bit of context: In our current setup, we use both slack and jira integrations. Upon new report, sentry also creates a jira ticked, linked with it. Integrations provide status synchronization, that part works great. Sentry bot sends updates to the dedicated channel.
The problem:
Any status changes made on jira are not being posted on the channel, only the ones made directly on setnty.io or the channel itself.
Steps:
- Open jira task assigned with crash report
- Assign it to the user
- Notice that sentry report has now the same assignee
- Notice that there are no updates on the channel
Expected Result
Steps:
- Open jira task assigned with crash report
- Assign it to the user
- Notice that sentry report has now the same assignee
- Notice that there is a message on the channel, in a thread, that the issue was assigned to a user
Actual Result
Steps:
- Open jira task assigned with crash report
- Assign it to the user
- No updates on the channel
Product Area
Alerts
Link
No response
DSN
No response
Version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names the Jira-to-Sentry status synchronization and Sentry Slack channel notification paths, but no repository files or tests. Start by tracing those integration entry points, reproduce an assignee change in Jira, and verify that a threaded channel update is emitted for the synchronized assignment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100