How to Add a Flag in Jira

You’re in a sprint planning meeting. Someone asks about a ticket that’s been sitting untouched for three days. Nobody flagged it. Nobody escalated it. And now your whole sprint is at risk because one blocked issue slipped through the cracks.

That’s exactly what Jira flags are built to prevent.

A flag in Jira is a visual marker — a small but powerful signal — that tells your entire team: this issue needs attention right now. It turns invisible blockers into visible priorities without requiring a Slack message, a comment, or a meeting.

This guide walks you through exactly how to add a flag in Jira, where flags show up across your board, and how to use them to keep work moving instead of stalling.

What Is a Flag in Jira?

A flag in Jira is a visual indicator applied to an issue to signal that it is blocked, at risk, or needs immediate attention. Flagged issues typically appear with a distinct color — usually orange or yellow — on your board, making them instantly visible to everyone on the team.

Flags don’t change the status of an issue. They don’t reassign it or move it through the workflow. They simply say: something is wrong here, and someone needs to look at this.

According to Atlassian’s own research, teams that actively surface blockers and impediments resolve them 2–3x faster than teams that rely on status updates alone. Flags are a lightweight, zero-friction way to surface those blockers in real time.

Key things to know about Jira flags:

• They appear across the board view, backlog, and issue detail view
• Any team member can add or remove a flag — no admin access required
• You can add an optional comment when flagging an issue to explain the blocker
• Flags are visible in sprint reports and board filters

Why Flagging Issues Matters More Than You Think

Most teams underestimate how much invisible blockers cost them.

A 2023 report by the Project Management Institute found that 12% of all project spend is wasted due to poor risk identification and escalation. In software teams specifically, blockers that go unaddressed for more than 24 hours are far more likely to cause sprint failure.

Jira flags give teams a consistent, shared language for escalation. Instead of hoping someone reads a comment buried three levels deep in a thread, a flag puts the issue front and center on the board where the entire team can see it during standups, reviews, and planning sessions.

Teams using Jira actively — with flags, blockers, and impediment tracking — report up to 34% higher on-time sprint completion rates compared to teams that don’t use these features.

How to Add a Flag in Jira (Board View)

The fastest way to add a flag is directly from your board. Here’s how:

Step 1: Open your active sprint board

Navigate to your Jira project and go to the board where your current sprint issues are displayed.

Step 2: Right-click on the issue card

On the board, right-click directly on the issue card you want to flag. A context menu will appear.

Step 3: Select “Add flag”

Click Add flag from the context menu. A dialog box will appear prompting you to add an optional comment explaining why the issue is being flagged.

Step 4: Add a comment (optional but recommended)

Type a brief reason for flagging — for example, “Blocked on third-party API access” or “Waiting for design sign-off.” This gives your team immediate context without requiring anyone to dig into comments.

Step 5: Confirm

Click Add to apply the flag. The issue card will immediately change color (typically to an orange highlight) on the board, signaling to everyone that this issue needs attention.

How to Add a Flag from the Issue Detail View

If you prefer to flag an issue while reviewing its details, you can do it directly from the issue page:

Step 1: Open the issue

Click on any issue from the board, backlog, or search results to open its detail view.

Step 2: Click the flag icon

In the issue detail view, look for the flag icon in the top-right action area (it may appear under the “…” more options menu depending on your Jira configuration and version).

Step 3: Select “Add flag”

Click Add flag. An optional comment field will appear.

Step 4: Add context and confirm

Add a brief explanation if needed, then confirm. The flag is now applied and visible across all board and backlog views.

How to Add a Flag from the Backlog

Flags aren’t just for active sprint issues — you can also flag backlog items to indicate they’re blocked before they even enter a sprint.

Step 1: Go to your project backlog

Navigate to Project > Backlog in the left sidebar.

Step 2: Right-click the issue

Right-click on the issue you want to flag in the backlog list.

Step 3: Select “Add flag”

Choose Add flag from the context menu and add an optional comment.

Step 4: Confirm

Click Add. The issue will now display a flag icon next to it in the backlog, making it visible during sprint planning discussions.

How to Remove a Flag in Jira

Removing a flag is just as simple as adding one — and it’s important to do it once the blocker is resolved so the team doesn’t waste time investigating resolved issues.

From the board:

Right-click the flagged issue card and select Remove flag from the context menu.

From the issue detail view:

Open the issue, click the flag icon or find it under the “…” menu, and select Remove flag.

The issue card will immediately return to its normal color, indicating the blocker has been resolved.

How Flags Appear Across Jira Views

Understanding where flags show up helps you use them strategically:

Board view: Flagged issues appear highlighted (usually orange) and stand out immediately during standups. This is the primary place most teams notice flags.

Backlog: Flags appear as a small icon next to the issue title, making blocked backlog items easy to identify during planning sessions.

Issue detail view: A flag indicator appears at the top of the issue, along with any flag comment that was added.

Filters and JQL: You can query flagged issues using Jira Query Language (JQL) with the filter flagged = Impediment. This lets you build dashboards, reports, and board filters specifically around blocked work.

For example, a team tracking blocked issues at scale can run a report showing all flagged items across multiple projects — giving leadership a real-time view of impediments without requiring status calls.

Best Practices for Using Flags Effectively

Knowing how to add a flag is step one. Using flags in a way that actually improves team performance is step two.

Flag early, not late. The moment an issue becomes blocked, flag it. Waiting until standup the next day means losing 18–24 hours of resolution time.

Always add a comment. A flag without context forces someone else to investigate. A flag with a one-line comment like “Waiting on legal approval” gives the team immediate clarity and lets the right person act without back-and-forth.

Make flags part of your standup ritual. Scan for flagged issues at the start of every standup. Teams that review impediments daily resolve them significantly faster. Research shows daily blocker reviews reduce average resolution time by up to 40% compared to teams that review blockers weekly.

Remove flags promptly when resolved. Old flags create noise. If your board has three flagged issues from two weeks ago, the team stops taking flags seriously. A clean flag system is a trusted flag system.

Use JQL to track flag trends. If certain team members or issue types get flagged repeatedly, that’s a signal worth investigating. A recurring flag pattern often points to a systemic process problem, not a one-off blocker.

Common Questions About Jira Flags

Can multiple people flag the same issue?

Yes. If a flag is already applied, adding another flag simply updates the comment. The issue remains flagged — it doesn’t stack multiple flags.

Do flags affect sprint velocity or reporting?

Flags themselves don’t directly impact velocity calculations, but they’re valuable inputs for sprint retrospectives. Many teams track the number of flagged issues per sprint as a leading indicator of process health.

Can you filter for flagged issues in Jira?

Yes. Use the JQL query flagged = Impediment in the issue navigator to find all currently flagged issues. You can save this as a filter and add it to your dashboard for ongoing visibility.

Are flags available in all Jira plans?

Flagging is available in Jira Software across Free, Standard, and Premium plans. The feature works in both company-managed and team-managed projects.

Who gets notified when an issue is flagged?

By default, flagging an issue doesn’t trigger a notification. The flag is a visual signal on the board. If you need to alert a specific person, pair the flag with an @mention in the comment field — that will trigger a Jira notification to the mentioned user.