How to Add CC in Jira Comment

If you’ve ever wanted to loop someone into a Jira comment — a colleague, a client, a manager — and wondered why there’s no obvious “CC” field, you’re not alone. Jira doesn’t work like email. But that doesn’t mean you’re stuck.

There are several ways to make sure the right people see the right updates. This guide walks you through all of them, step by step.

Why Jira Doesn’t Have a Native CC Field

Jira is built around issues, watchers, and notifications — not inboxes. Instead of CC-ing someone the way you would in an email, Jira routes updates through its own notification and mention system.

According to Atlassian’s own product data, over 65,000 companies use Jira globally, and one of the most common support questions revolves around notification and mention behavior. The learning curve isn’t about complexity — it’s about shifting from email thinking to issue-tracking thinking.

Once you understand the three core mechanisms Jira uses, getting the right people notified becomes second nature.

The Three Ways to “CC” Someone in Jira

Use @mention in Your Comment

This is the closest thing to a direct CC in a Jira comment.

When you type @ followed by a username or display name inside a comment, that person receives an email notification — even if they’re not watching the issue.

How to do it:

1. Open the Jira issue you want to comment on
2. Click “Add a comment” at the bottom of the issue
3. Inside the comment text box, type @ and start typing the person’s name
4. Select their name from the dropdown that appears
5. Finish writing your comment
6. Click Save

The mentioned user will receive an email notification with a link to the issue. They can then choose to watch the issue for future updates.

Pro tip: You can @mention multiple people in the same comment. There’s no limit, so loop in as many stakeholders as needed.

Add Someone as a Watcher

If you want someone to receive all future notifications on an issue — not just for one comment — add them as a Watcher.

How to do it:

1. Open the Jira issue
2. Look for the “Watch” section in the right-hand details panel (it shows the current number of watchers)
3. Click the number or the eye icon
4. In the dialog that opens, click “Add watchers”
5. Search for the person by name or email
6. Select them and confirm

They’ll now receive notifications every time the issue is updated, commented on, or moved through workflow stages.

Studies show that teams using structured notification settings in project management tools see up to 30% fewer missed deadlines — simply because the right people stay informed in real time.

Use the “Share” Feature on an Issue

For a one-time heads-up — where you don’t want to add someone as a permanent watcher — Jira’s Share feature works well.

How to do it:

1. Open the Jira issue
2. Click the Share button (usually represented by a link or share icon near the top-right of the issue)
3. Enter the person’s email address or username
4. Add an optional message
5. Click Share

They’ll receive an email with a direct link to the issue. Clean, simple, no comment clutter.

How to CC Multiple People at Once

Sometimes you need to notify an entire team or group. Here’s how to scale it:

Option 1 — @mention multiple people in one comment Simply type @Name1 @Name2 @Name3 in your comment. Each person gets their own notification.

Option 2 — Mention a team or group (if configured) If your Jira admin has set up user groups, you can @mention the group name and every member in that group receives a notification. This is especially useful for cross-functional updates.

Option 3 — Use automation rules Jira’s built-in automation (available in Jira Cloud) allows you to create rules like: “When a comment is added and contains keyword X, notify user group Y.” This is powerful for recurring workflows where the same people always need to be in the loop.

According to Atlassian, teams that use Jira automation rules save an average of 4+ hours per week in manual follow-up and status updates.

Managing Notification Settings So CC’s Don’t Get Ignored

Here’s the problem most teams run into: they @mention someone, that person’s inbox is already flooded with Jira notifications, and the important comment gets buried.

Here’s how to fix that:

For individuals

• Go to your Profile Settings in Jira
• Navigate to Notification preferences
• Choose which events trigger emails vs. in-app only vs. no notification

For admins

• Go to Project Settings → Notifications
• Customize the Notification Scheme to define who gets notified for what events
• You can set rules for comments specifically — separate from general issue updates

Research from McKinsey shows that workers spend 28% of their workweek managing emails. Cleaning up Jira notification schemes reduces this significantly by ensuring alerts are relevant and expected.

Common Issues and How to Fix Them

The @mentioned person didn’t receive a notification

Possible causes:

• They don’t have a Jira account — external users can’t be @mentioned
• Their notification settings have email alerts disabled
• The Jira admin has restricted notifications at the project level

Fix: Check their notification preferences, or ask your Jira admin to review the project’s notification scheme.

You can’t find someone in the @mention dropdown

Possible causes:

• They haven’t been added to the Jira project
• Their account isn’t active

Fix: Ask your admin to add them to the project, or verify their account status in User Management.

The Share button isn’t visible

This can happen on older Jira versions or when the feature has been restricted by the admin. Check with your Jira admin if you don’t see it.

Jira CC vs Email CC: Key Differences

The structured, traceable nature of Jira notifications is one reason 75% of Fortune 500 companies use Atlassian products for project collaboration — the data trail is built in.

Conclusion

Jira doesn’t have a CC field — but it gives you something better: a system where notifications are structured, traceable, and tied directly to the work being done. Whether you use @mentions for quick callouts, watchers for ongoing visibility, or automation for scaled teams, there’s a method that fits every use case.

The key is matching the right tool to the right situation. For one-off notifications, @mention works perfectly. For long-running issues, add watchers. For external sharing, use the Share feature. And for recurring workflows, set up automation rules once and let Jira handle the rest.

Notifications that reach the right people at the right time aren’t just a convenience — they’re what keeps projects moving and teams aligned.