PII Detections by Project(5.4.5)

Personal data should not appear in Jira issue summaries or comments. When it does, whether an email address, a phone number, or a personal ID number, that is personal data sitting in a field that was probably not intended to hold it, and your data protection function decides what follows. This visual shows how detections are distributed across projects and which patterns are appearing most frequently.

What you can conclude

• A project with a high detection count has a data hygiene question worth asking: team members may be routinely including personal data in issue text that should be kept out of the tracker.
• The dominant type tells you what to focus on in training and process: email addresses are often copy-pasted from support tickets, phone-shaped digits from customer records.
• A project with zero detections is either very clean or has very low textual data in issues, so context matters.

How this chart works

Stacked bar chart of detection counts per project, broken down by pattern (email address, phone-shaped digits, numeric ID). Each issue is counted once per type, so an issue matching two patterns appears in both bars. Use the date and project filters to focus on specific periods.

What each pattern actually matches. Email is a conventional address pattern and is the most reliable of the three. Phone-shaped digits means a standalone run of 7 to 15 digits that does not parse as a calendar date or a timestamp; runs that do parse as dates (20260421) or timestamps (20260730180000) are excluded, but a build number or an account reference of the right length will still match. Numeric ID is a standalone run of 6 to 12 digits and is the loosest of the three. Only the email bar should be read as near-certain.

Teams preparing a GDPR review commonly start here to see where personal data is concentrated.