How to blur a Jira screenshot
Assignees, customer names in tickets, and issue URLs. Cover them before the bug report leaves your org.
Filing a Jira screenshot into a public tracker or a vendor Slack? Assignees, customer names in the summary, and the issue URL often ride along with the “steps to reproduce.” Cover the people and domains that are not the bug in Paint, Preview, or a browser tab — then send that copy, not the raw board still open in another tab.
How to blur a Jira screenshot (step by step)
Bar or crop the left project nav and the top search first. Recent issues and filter chips often name customers you are not talking about.
On your phone or computer
Windows: Capture with Win + Shift + S, open in Paint, and drop filled rectangles over assignees, customer names in the summary, and the address bar.
Mac: Preview → Markup with a filled shape over Reporter / Watchers and any email in comments.
Prefer opaque covers for emails and issue URLs that name a private tenant — soft blur on short strings is weak.
Or finish in a browser (optional)
Want to do it in a tab with no install? BlurThis is one free option. The file stays on your device. Other browser tools work too if they paint on the page and do not upload the image.
- Open the editor in your browser. No account needed for BlurThis.
- Drop the screenshot, tap Upload from PC or Mobile, or paste with Ctrl / ⌘ + V on a computer.
- Pick Box or Draw. Use Black bar for phone numbers, emails, and OTPs. Use Blur for faces when a soft cover is enough.
- Drag over each private spot. Pinch or use + / − to zoom. Leave a little padding so no letter peeks out.
- Tap Download PNG. Send that file. Keep the original out of the chat or ticket.
What to cover in the Jira chrome
- Summary and description text that embeds a customer company, email, or phone.
- Assignee, Reporter, and Watchers — faces and display names in the people fields.
- Comments and @mentions that reprint internal emails or Slack handles.
- Attachments list filenames that include account IDs or contract numbers.
- Breadcrumbs and project keys that identify a private tenant when the ticket goes outside.
- Browser address bar: site URL, issue key, and any query tokens.
Crop to the failing UI panel when that panel is the proof. You skip the people fields and the activity stream. If you must show the whole issue, bar every name plate that repeats between summary and comments.
Black bar for names, emails, and URLs
Email addresses, phone numbers, and order IDs pasted into the description are short strings. Soft blur fails on those. Use Black bar over any digit-heavy field and over the full address bar if the URL holds a secret or a customer slug. Display names that are just a work email get the same bar.
Tokens in the URL are a classic leak when you snip “the ticket.” Cover the whole bar, not just the tab title — the longer version is in hide an API key in the URL bar. For bug-report hygiene in general, see redact a bug-report screenshot.
Boards, backlogs, and dashboards
A board screenshot is a roster of epics and owners. Crop to one card if that card is the bug. Backlog captures leak story points next to customer-facing titles. Dashboard gadgets often pull filter results with emails in custom fields — bar those columns or leave the gadget out of the frame.
Pasting the same snip into Slack needs the sidebar covered too. The workspace rules are in blur a Slack screenshot.
FAQ: Do I cover the issue key?
Inside your org, the key is usually fine. On a public forum or a competitor-facing deck, bar or crop it if the key encodes a customer or a private project name.
FAQ: What about Confluence embeds?
Embedded pages and smart links can unroll a title with a person’s name. Bar the embed chrome the same way you bar a comment.
FAQ: Can I rely on Jira’s “hide from customer”?
That setting controls who sees the live ticket. It does not rewrite a PNG you already exported. Bar the file before you attach it elsewhere.
FAQ: Service Management vs Software?
Service tickets lean harder on requester email and organization fields. Software boards lean on assignees and sprint names. Cover whichever column is not the bug.