Skip to main content

5 posts tagged with "jira"

View All Tags

Historical Scanning now available for Jira Data Center

calendar icon   Release Date: July 7, 2025

Jira DC Historical Scan Thumbnail

Following the introduction of the historical scanning for Confluence Data Center, we’ve kept the pace with the support of that capability for Jira Data Center!

What's new?

Previously, our integration would surface hardcoded secrets in real-time, alerting you to newly introduced risks as soon as they appeared. With this update, we’re extending our detection to include secrets that were leaked in the past—not just those introduced going forward.

Why does this matter?

Once a secret is leaked, it should always be considered compromised, regardless of when the leak occurred. By surfacing historical secrets, you can now:

  • Identify and remediate old, forgotten leaks that may still pose a security risk.
  • Reach a comprehensive security posture by ensuring that no secrets—past or present—slip through the cracks.
  • Take proactive action to rotate or revoke secrets that may have been exposed long ago.

Check out our Jira Data Center documentation to see how to use this feature now!


Fixes

  • Email Notifications: Improved email delivery logic for Microsoft Teams integrations to prevent excessive notification sending during periodic scans.

Historical Scanning now available for Jira and Confluence Cloud sources.

calendar icon   Release Date: April 29, 2025

Jira Confluence historical scan Thumbnail

We’re excited to announce a significant enhancement to our secret detection capabilities for Jira and Confluence Cloud: historical scanning is now available!

What's new?

Previously, our integration would surface hardcoded secrets in real-time, alerting you to newly introduced risks as soon as they appeared. With this update, we’re extending our detection to include secrets that were leaked in the past—not just those introduced going forward.

Why does this matter?

Once a secret is leaked, it should always be considered compromised, regardless of when the leak occurred. By surfacing historical secrets, you can now:

  • Identify and remediate old, forgotten leaks that may still pose a security risk.
  • Reach a comprehensive security posture by ensuring that no secrets—past or present—slip through the cracks.
  • Take proactive action to rotate or revoke secrets that may have been exposed long ago.

Check out our documentation to enable the feature now:


Enhancements

  • API: Introduced a new endpoint GET to the Public API, allowing users to retrieve invitation details.

Fixes

  • ServiceNow Integration: Redirects to the proper URL when checking hardcoded secrets in ServiceNow sources.

Enhanced email incident alerting controls for members

calendar icon   Release Date: February 27, 2025

![email alerting](/img/release-note/email-incident-alerting thumbnail.png) You can now manage email notification settings more effectively with an option that allow updates through the API, and customize account-level defaults, ensuring a more tailored communication experience for all members. Learn more


Enhancements

  • Jira Issue Tracking Integration:
    • Added Incident ID as an optional variable in Jira ticket templates for improved customization.
    • Enabled instant ticket creation in Jira without requiring a predefined template.

Fixes

  • Users & Teams:
    • Incidents: Resolved an issue where restricted users could not view the Vulnerable Sources block.

Search incidents by secret value

calendar icon   Release Date: February 11, 2025

search secret GitGuardian allows you to monitor secret leaks across thousands of your repositories and over 30 different types of sources. It is reassuring to know that this critical secret, which provides access to your corporate LDAP, has not been detected anywhere.


Enhancements

  • Scan Only Addition Lines in Commits: Now, when using ggshield or our check runs integration, we only scan for added lines in commits. Developers will no longer be blocked while remediating incidents.
  • Jira Issue Tracking Integration: Added support for "Numbers (or float)" and "Group Pickers (single group)" custom fields in Jira templates, allowing more customization in notifications and issue tracking.

Fixes

  • GitLab Integration: Resolved an issue where GitLab installations were incorrectly revoked due to temporary plan downgrades or admin status changes.
  • Confluence Cloud Integration: Fixed an issue where some Confluence Cloud events without a spaceKey were incorrectly ignored.
  • Incidents: Resolved an issue where restricted users could not view the Vulnerable Sources block.
  • Teams Management: Resolved an issue where action menus were not displayed in the teammates table for non-admin users in certain cases.
  • Email Notifications: Fixed an issue where emails for ignored and valid incidents were sent to all teams a user belongs to, instead of only the teams managing the affected repository.

Bitbucket Cloud scanning, Microsoft Teams alerts & Jira issue tracking

calendar icon   Release Date: January 13, 2025

Bitbucket Cloud Scanning

Bitbucket Cloud Integration Secure your Bitbucket Cloud repositories with secrets detection powered by GitGuardian.

  • Detect exposed credentials and secrets in real-time.
  • Gain visibility into security incidents directly in your dashboard.
    Learn more

Microsoft Teams Security Alerts

MS team alerting Never miss a critical security event with real-time GitGuardian alerts in Microsoft Teams.

  • Instant notifications when security incidents occur.
  • Direct links to investigate issues inside GitGuardian.
    Learn more

Jira Data Center Auto-Tracking for Security Incidents

jira dc alerting Streamline incident response with Jira Data Center integration.

  • Auto-create Jira issues when new incidents are detected.
  • Sync custom fields for better tracking.
  • Auto-resolve incidents when Jira issues are closed.
    Learn more

Fixes

  • User Management: Fixed an issue preventing user deletion when associated with saved views.
  • Azure Repos Sync: Improved detection and syncing of deleted organizations when using all-org access tokens.