How to Blur Jira Tickets During Sprint Demos and Screen Sharing

Short answer

Hide confidential project names, ticket details, assignees, and client information in Jira before sprint demos, standup calls, and stakeholder presentations.

Direct answer

hide confidential project names, ticket details, assignees, and client information in jira before sprint demos, standup calls, and stakeholder presentations and follow the step-by-step approach in this guide.

The Sprint Demo Exposure Problem

Sprint demos are supposed to showcase completed work. In practice, they showcase everything visible on your Jira board: ticket titles for features not yet announced, bug descriptions with customer names, story points revealing team capacity, assignee names showing who is working on what, and linked issues referencing other projects.

Jira boards are information-dense. A single board view typically displays 20-50 tickets across multiple columns, each with a title, assignee avatar, priority flag, and sometimes story points and labels. When you share this screen during a sprint demo, every participant sees every ticket — including stakeholders, clients, and team members from other projects.

This is especially problematic for:

• Agencies running multiple client projects on one Jira instance
• Product teams with unreleased features visible on the board
• Consulting firms where project names reveal client identities
• Enterprise teams with confidential security or compliance tickets

What to Blur on Jira

Board View (Kanban/Scrum)

• Ticket titles containing feature names, client references, or sensitive keywords
• Assignee names and avatars (if team composition is confidential)
• Story points (if team velocity is sensitive)
• Labels and tags referencing other projects or clients
• Swimlane headers that group by client or project

Backlog View

• Tickets from other sprints or projects visible in the sidebar
• Epic names that reveal product roadmap
• Priority rankings that show business priorities

Individual Ticket View

• Description text with client names, user reports, or internal details
• Comments with team discussions and decisions
• Attachments showing screenshots with sensitive data
• Linked issues referencing other projects
• Reporter and assignee names

Dashboard

• Sprint burndown charts (shows team capacity and velocity)
• JQL filter results showing tickets from multiple projects
• Activity stream with comments and status changes across projects

How to Blur Jira for Sprint Demos

1. Open your Jira board in Chrome before the demo
2. Activate ContextBlur (Ctrl+Shift+B)
3. Click ticket titles you want to hide — unrelated tickets, unreleased features, client names
4. Click assignee names or avatars if team composition is confidential
5. Click any dashboard metrics or backlog items visible in the sidebar
6. Start the sprint demo — blurred elements remain hidden while you present

Navigate between tickets during the demo. When you return to the board view, your blurs are still in place.

Scenario Strategies

Client Sprint Demos

When demoing to a client who shares your Jira instance with other clients:

• Blur all ticket titles from other client projects
• Blur swimlane headers that reference other clients
• Blur backlog items not relevant to this client
• Blur any linked issues pointing to internal or other-client work

Internal Sprint Demos with Mixed Audiences

When team members from other departments join your sprint demo:

• Blur security vulnerability tickets
• Blur tickets about employee-related features (HR tools, performance tracking)
• Blur story points if velocity data is sensitive
• Blur assignees if reporting structure is confidential

Stakeholder Presentations

When presenting Jira boards to executives or board members:

• Blur technical ticket titles and show only epics
• Blur individual assignees (show team-level progress)
• Blur bug tickets and focus on feature completions
• Blur story points and use percentage completion instead

Open Source Project Demos

If you manage both public and private projects:

• Blur all private project tickets visible in sidebars
• Blur customer-reported issues with identifying information
• Blur internal labels and tags

Pro Tip: Filter First, Then Blur

Jira's built-in filters can reduce what is visible on the board. Before a screen share:

1. Apply a JQL filter to show only relevant tickets
2. Switch to a board view that filters by sprint, epic, or label
3. Then use ContextBlur to blur anything that still leaks through

Filtering reduces the blurring workload. Blurring catches what filters miss.

Auto-Blur for Jira

ContextBlur Pro auto-detects email addresses and other sensitive patterns that appear in Jira ticket descriptions, comments, and reporter fields. Set up auto-blur once and it catches PII in tickets automatically on every visit.

For teams that demo Jira daily during standups, this eliminates the need for manual pre-meeting preparation.

Check our screen sharing checklist for the full 30-second routine, and our developer screen sharing guide for more developer-specific privacy strategies.