Semgrep: Jira tickets not being associated with findings
Timeline of updates
- resolved
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 Semgrep’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.semgrep.dev (opens in new tab).
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).
- Title
- Jira tickets not being associated with findings
- Vendor
- Semgrep
- Date
- URL
- https://rewindex.com/company/semgrep/incidents/b87pvj454cp3
Semgrep profileRecent Semgrep incidentsAll outages on September 11, 2024Semgrep in September 2024MarkdownJSON