Dependabot does not update Jira when an alert gets deleted

[akerge]

Select Topic Area

Bug

Body

👋

Problem Description

We have integration between Jira and GitHub. Whenever a Dependabot creates an alert a PR and a finding in Jira Security is created. When a developer comments @Dependabot rebase in the created PR, that PR gets closed and Dependabot adds a comment that the PR is superseded by another. That is expected behavior. BUT the Dependabot alert gets deleted AND the finding in Jira does not get updated leaving the team with a dangling finding. Most probably due to a missing webhook.

What We've Tried

Re-syncing (backfilling) GitHub data to Jira as per instructions (JRACLOUD-86035, JRACLOUD-86039) failed to resolve the dangling finding in Jira.

Has anyone else experienced something similar? How did you resolve the dangling finding in Jira?

Edit: add link to Jira security feature

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐