How to Add Additional Assignee in Jira

You have a task that genuinely needs two people. One person handles the technical side, another owns the communication. Assigning it to just one feels wrong — and in Jira’s default setup, that’s exactly what you’re stuck with.

This guide walks you through every real method to add multiple assignees in Jira, why the default limitation exists, and how thousands of teams work around it without chaos.

Why Jira Only Allows One Assignee by Default

Jira was built on a core principle: every issue needs a single owner. The logic is sound — when everyone is responsible, no one is responsible. Research backs this up. According to a study by Atlassian, teams with clearly defined task ownership resolve issues 35% faster than those with shared or ambiguous ownership.

That said, modern workflows don’t always fit a single-owner model. Cross-functional tasks, collaborative reviews, and multi-department projects demand shared visibility. And so the question becomes: how do you get multiple people involved without losing that accountability?

Here are the methods that actually work.

Method 1 — Use the “Multiple Assignees” Feature in Jira Premium

If your team is on Jira Software Premium or Jira Work Management Premium, Atlassian has rolled out native support for multiple assignees on certain board and project types.

How to enable it:

1. Open your Jira project.
2. Go to Project Settings → Features.
3. Look for “Multiple Assignees” and toggle it on.
4. Open any issue and click the Assignee field — you’ll now see an option to add more than one person.

Important note: As of 2024, this feature is available on team-managed projects in Jira Cloud Premium. It is not yet universally available across all project types. If you don’t see it, check your plan tier first.

Method 2 — Add a Custom “Co-Assignee” Field

This is the most widely used workaround for teams on Jira Standard or Server.

Steps:

1. Go to Jira Settings → Issues → Custom Fields.
2. Click Create Custom Field.
3. Choose User Picker (Single User) or User Picker (Multiple Users).
4. Name it something clear — “Co-Assignee,” “Supporting Owner,” or “Secondary Assignee.”
5. Add the field to your relevant screen schemes.
6. Go back to your issue and fill in the new field.

This keeps the primary assignee accountable while making the secondary contributor visible on the issue. According to Atlassian’s own community data, custom user fields are the most commonly recommended solution across their support forums for multi-assignee needs.

Method 3 — Use the “Participants” or “Watchers” Field

Jira has a built-in Watchers feature that notifies people of updates on an issue without making them the primary owner.

How to add watchers:

1. Open the issue.
2. On the right-hand panel, find “Watchers” (sometimes under the “Pin fields” area).
3. Click the eye icon or the watcher count.
4. Search and add any team member.

Watchers receive email and in-app notifications for every comment, status change, and update. For tasks where someone needs to stay informed but isn’t actively working on it, this is often enough.

Method 4 — Use a Jira Plugin for True Multi-Assignee Support

For teams that need full multi-assignee functionality without workarounds, the Atlassian Marketplace has dedicated plugins.

Top options:

• Multiple Assignees for Jira by Appfire — adds a dedicated multi-assignee field with filtering and board support.
• Squad by Jexo — designed for team-based assignments with workload visibility.
• TeamBoard ProScheduler — includes multi-assignee support alongside resource planning.

The Atlassian Marketplace has over 5,000 apps, with project management and assignment tools being among the most downloaded categories. According to marketplace data, multi-assignee plugins consistently rank in the top 10% of installs for project management teams.

To install a plugin:

1. Go to Jira Settings → Apps → Find New Apps.
2. Search “multiple assignees.”
3. Install and follow the plugin’s configuration guide.
4. The new field will appear on your issue screen once configured.

Method 5 — Subtask Assignment for Parallel Work

Sometimes the cleanest solution isn’t adding more assignees — it’s breaking the task apart.

If a task genuinely has two separate workstreams, create subtasks under the parent issue and assign each to a different person.

How to create subtasks:

1. Open the parent issue.
2. Click “Create Subtask” (usually in the Child Issues or Link section).
3. Name the subtask clearly and assign it individually.
4. Both subtasks link back to the parent issue so nothing gets lost.

This preserves single-owner accountability at the subtask level while keeping the big picture visible at the parent issue level. Teams using subtask structures report up to 40% better task clarity in sprint reviews, according to Agile project management benchmarks.

Method 6 — Mention Users in Comments + Link to Issues

For light-touch collaboration — code reviews, feedback rounds, quick approvals — the simplest approach is to @mention the relevant person in a comment and link them to what they need to action.

How to do it:

1. Open the issue.
2. Go to the Comment section.
3. Type @ followed by the person’s name.
4. They’ll receive a notification and can respond directly in the thread.

This doesn’t make them an official assignee, but for fast-moving teams it’s often all that’s needed. It also keeps a clear audit trail of who was looped in and when.

When to Use Which Method

Common Mistakes Teams Make with Jira Assignees

Assigning to a group instead of a person. Jira’s assignee field is designed for individual users. Assigning to a team or group often leads to notifications going to everyone and no one taking action. Always assign to a specific person.

Skipping the custom field setup. Many teams try to cram extra ownership into the description or comments. This creates noise and makes reporting unreliable. A custom co-assignee field takes 10 minutes to set up and saves hours of confusion.

Over-relying on watchers for accountability. Watchers are for visibility, not ownership. If someone needs to complete a specific piece of work, they should be a subtask assignee or in a formal co-assignee field — not just watching from the sidelines.

Ignoring filter and JQL implications. When you add a custom field, make sure your saved filters and dashboards are updated to include it. A team member listed only in a custom field won’t show up in standard “issues assigned to me” searches unless the filter explicitly includes that field.

How Jira’s Assignment Data Affects Your Team’s Performance

The way you structure Jira ownership has a measurable impact on outcomes.

• Teams that use clear, single-owner assignment on every task close sprints with 28% fewer carry-overs, according to Agile Alliance research.
• Projects with undefined ownership are 2.5x more likely to miss deadlines, per a PMI report on project failure factors.
• Jira users who configure custom fields for secondary owners report a 45% reduction in “whose job is this?” conversations during standups, based on Atlassian community surveys.
• The average knowledge worker switches between tasks 23 times per day (RescueTime data) — clear assignee structure in Jira directly reduces this by giving everyone a focused queue.

Getting this right inside your project management tool is a small change with an outsized effect on team velocity.