# Semgrep: Jira tickets not being associated with findings

> Semgrep status incident “Jira tickets not being associated with findings” on 2024-09-11: impact minor (vendor’s label), 30 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/semgrep/incidents/b87pvj454cp3
Last updated: 2024-09-13T01:29:00Z

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2024-09-11 19:03 UTC · Resolved: 2024-09-13 01:29 UTC · Duration: 30 h
- Updates: 1
- [Vendor status page: https://status.semgrep.dev/incidents/b87pvj454cp3](https://status.semgrep.dev/incidents/b87pvj454cp3)
- [Company: Semgrep](https://rewindex.com/company/semgrep.md)

## Timeline of updates

- **resolved** 2024-09-13 01:29 UTC: We've backfilled associations between findings and Jira tickets, and have gathered a list of duplicate Jira tickets created during the outage for affected deployments. We will reach out to affected customers for next steps.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## Cite this

Status incident (vendor impact label: minor) posted by Semgrep, started 2024-09-11 19:03 UTC, resolved after 30 h, 1 update(s).

- Canonical URL: https://rewindex.com/company/semgrep/incidents/b87pvj454cp3
- Citation: Semgrep, “Jira tickets not being associated with findings” (2024-09-11 19:03 UTC). Archived by Rewindex: https://rewindex.com/company/semgrep/incidents/b87pvj454cp3 (CC BY 4.0).
- Markdown link: `[Semgrep: Jira tickets not being associated with findings (2024-09-11)](https://rewindex.com/company/semgrep/incidents/b87pvj454cp3)`


---
Canonical: https://rewindex.com/company/semgrep/incidents/b87pvj454cp3 · Markdown: https://rewindex.com/company/semgrep/incidents/b87pvj454cp3.md · JSON: https://rewindex.com/api/v1/companies/semgrep/incidents/b87pvj454cp3 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T15:18:40.341Z