How we automated Jira issue assignment and what Atlassian's Rising Star recognition means to us

[#1]

When we started building SnapAssign - Smart Assignments for Jira, the problem we were trying to solve was straightforward: in almost every Jira team we talked to, issue assignment was still manual. Someone usually a team lead or project manager was spending real time every day deciding who should get what. And even then, the distribution was rarely balanced.

We wanted to change that. SnapAssign - Smart Assignments for Jira automates issue assignment in Jira using configurable rules based on round-robin rotation, workload balancing, and shift calendars. No code, no scripts, no Jira automation rule chains to maintain.

A few weeks ago, Atlassian featured SnapAssign - Smart Assignments for Jira as a Rising Star on the Marketplace  a recognition given to newer apps that have shown notable growth and high ratings in a short time. We’re grateful for that, and it felt like a good moment to properly introduce the app to this community.

The Problem We’re Solving

Manual issue assignment in Jira creates a few recurring headaches:

• Issues sit unassigned for too long while someone figures out who should take them.
• Work piles up unevenly some people are overloaded, others have capacity that’s invisible to the team.
• Leads spend time on coordination that shouldn’t need their attention.
• In teams that span time zones or shifts, assignment gaps appear whenever the “right person” isn’t online.

SnapAssign - Smart Assignments for Jira addresses all of these through automated assignment rules that run inside your existing Jira workflows.

How it fits into Jira

SnapAssign - Smart Assignments for Jira uses Jira post functions to trigger assignments during workflow transitions. When an issue moves to a status that matches a rule, the app evaluates the rule and assigns automatically. No separate trigger, no manual step.

Three Assignment Methods

The core of SnapAssign - Smart Assignments for Jira is its three assignment methods. Each is designed for a different working style:

Round Robin	Load-Based	Shift-Based
Issues are assigned to team members in a rotating sequence. Each person gets an equal number of issues over time regardless of complexity. Best for: teams handling similarly scoped tasks where equal distribution matters most.	The next issue goes to whoever has the lightest current workload — measured by open issue count, Story Points, or the sum of any numeric custom field. Best for: teams with varied task sizes where balancing actual effort matters.	Assignments trigger only during defined working hours and shift calendars. If no one is available, the issue is held and reassigned at the start of the next shift. Best for: distributed or 24/7 teams operating across time zones.

Load-Based: Three Ways to Measure Workload

Load-based assignment is more nuanced than it might seem. SnapAssign - Smart Assignments for Jira gives you three ways to calculate who has the lightest load:

Load-Based Assignment: Three Calculation Methods
Method	How it works
By open issue count	The team member with the fewest currently assigned open issues gets the next one. Fast, simple, effective for uniform task sizes.
By sum of a numeric field	Totals a field like Story Points or Estimated Hours per person. The member with the lowest total gets assigned. Accounts for effort, not just count.
By sum of a dropdown field	Uses weighted dropdown values (e.g. priority levels) to calculate load. Assigns to the member with the lowest weighted total.

How Rules Work

Every assignment is driven by a rule. Rules are configured per team and can be as simple or as specific as you need. Here’s how you set one up:

Setting Up an Assignment Rule: Step by Step
#	Step	Details
1	Select a team	Choose which team the rule applies to.
2	Name the rule & set source projects	Define the issue source. Use “+More” to add filters: Status, Issue Type, Priority, saved Filters, or raw JQL.
3	Choose an assignment method	Round Robin or Load-Based. Configure options: assign only if unassigned, assign only once per rule, delay to next shift if no one is available.
4	Define shifts	Set working hours, calendars, and which team members are assignable during each shift.
5	Save	The rule goes live immediately and triggers automatically on matching workflow transitions.

Each team also gets a Default Assignment Rule — a fallback that catches any issue that doesn’t match a more specific rule. This means no issue can slip through unassigned. The default rule can’t be deleted, but it can be edited to adjust team members and the calendar it uses.

Three useful options worth knowing about

• Assign only if unassigned: Skip the rule if the issue already has an assignee.
• Assign only once per rule: Even if an issue triggers the rule multiple times, it only gets assigned by it once.
• Delay to next shift: If no one is available, the issue is flagged and a scheduler re-checks it at the start of the next shift.

Everything SnapAssign - Smart Assignments for Jira Includes

SnapAssign - Smart Assignments for Jira: Full Feature List
Feature	What it does
Load-Based Assignment	Assign based on open issue count, Story Points, or any numeric/dropdown custom field. The person with the lightest load gets the next issue.
Round Robin Assignment	Rotate assignments evenly across the team. Simple, fair, no configuration overhead.
Shift-Based Assignment	Define working hours, time zones, and shift calendars. Delay assignment to the next available shift when no one is on.
Customizable Rules	Filter by project, issue type, status, priority, or JQL. Stack multiple criteria to build rules that match exactly how your team works.
Jira Workflow Integration	Trigger assignments automatically via post functions during workflow transitions. No manual step needed.
Default Assignment Rule	A fallback rule ensures every issue gets assigned — even if it doesn’t match any specific rule.
Dashboard Gadgets	Visualize assignment activity and team workload directly on your Jira dashboard.
Real-Time Insights	See assignment events as they happen. No need to dig through logs.
Audit Logs	Every assignment attempt is logged — successes, failures, and reasons. Visible directly in the issue view.
No Coding Required	All rules are configured through a visual interface. No scripts, no automation rules to maintain.

What “Rising Star” Actually Means

For anyone unfamiliar with the Atlassian Marketplace badge system: Rising Star is one of three editorial badges Atlassian introduced in Q1 2024, alongside Bestseller and Spotlight.

Rising Star is given to newer apps that have shown notable growth in installs and ratings within a short period. It’s not a self-reported badge — Atlassian selects the apps. It’s also not a permanent status; it reflects momentum at a specific point in time.

We’re sharing this not to make a bigger deal of it than it is, but because it’s a useful signal when you’re evaluating a newer app: other teams have tried it, found it useful, and rated it positively. That’s the real story behind it.

If you’re evaluating automation tools for Jira issue assignment and haven’t tried SnapAssign - Smart Assignments for Jira yet, we think it’s worth a look. And if you have questions about how it handles a specific use case, drop them below — we’re active here and respond to every comment.

Want to give it a try?

SnapAssign - Smart Assignments for Jira install and try on Atlassian Marketplace.

→ Find us on Atlassian Marketplace