GPT AddIns Contributor

Thank you so much, @Kate C_ 💙 I’m really glad to be able to contribute my first article and be part of this amazing community. Big congratulations to everyone else who shared their first article too. excited to keep learning and growing together here! 🙌

Hi @Emma Haley , Jira natively supports only one assignee per issue, which is why you’re running into those limitations (like missing notifications and only showing one avatar on the board). If you’d like to assign multiple people to a ticket with proper notifications and visibility, you might want to try this app: GPT…

Hi @Evalaji Jones , Jira by default only allows one assignee per task, and the usual workaround is sub-tasks or linked issues (as you mentioned, not always ideal). If you’d like to assign multiple people directly without cluttering the board, you might want to check out this app: GPT Multiple Assignees for Jira . It lets…

Hi @Robert Rudolph , Jira only supports one assignee per issue by default, but if you need multiple people working on the same task, you can try this app: GPT Multiple Assignees for Jira . It lets you assign several users at once and helps cross-functional teams avoid bottlenecks.

@Rula s much appreciated ! 🙏

Thank you so much, @Rula s 🙏 I’m really glad to hear the app is already making a difference for your team. Feedback like yours means a lot and helps us keep improving the experience. We will be looking forward to hearing your thoughts if you come across any ideas or enhancements!

It seems as an amazing app

Thanks @Dave LIAO 😊 I’ll make sure to follow the forum guidelines. I’d be thrilled if you could give GPT Multiple Assignees a try — I’m excited to hear your feedback, especially if there’s anything we can enhance to make it even more useful. 🚀

Thank you @Piotr Bojko , The app was published just 4 days ago, I want this badge to show up. I am now trying to find the steps to show it.

Hi @Piotr Bojko , I wasn’t aware of the “NEW” badge — thanks for bringing it to my attention! I’ll check how to enable it and make sure it’s visible for the app.

Hi @Teodora V _Warsaw Dynamics_ Thank you for moving my post to the correct category — I appreciate your help in making sure it’s in the right place for the Atlassian Community to find it! 😊

This is such a clear and practical breakdown — love how you’ve connected the real-world pain points PMs face with an actual, in-Jira solution. The step-by-step walkthrough and the “what’s inside” section make it feel like you’re not just selling a tool, but actually teaching how to master cost tracking. Really solid work. 🙌

Hi Bill, I appreciate your thoughtful breakdown — you’ve raised several valid points about how teams and organizations typically approach work assignment in Jira. Our use case is focused specifically on cross-functional or collaborative work items, where multiple people (often from different specialties) are actively…

This looks amazing! I really like how Kanban Flow Metrics makes it so easy to see where things are moving smoothly and where we might need to step in — all right inside Jira. No extra tools, no messy spreadsheets, just clear and useful insights. Feels like something that could really help teams stay on track and improve…

I get where you’re coming from, and in workflows that are strictly single-owner, this approach isn’t necessary. But in many cross-functional scenarios — where a task legitimately requires input from multiple disciplines — relying on one assignee can create unnecessary bottlenecks or force teams into awkward workarounds…

I get your point — every team has its own way of managing assignments. This app is simply designed for those who prefer a more direct multi-assignee approach without relying on workarounds like technical users and filters.

Understood — Jira’s one-owner model works well for many teams. This app simply provides another option for those whose workflows benefit from multiple assignees. Different teams have different needs, and this is here for the ones who prefer that flexibility.

I appreciate you sharing your view on this. For certain teams, keeping just one assignee is a great way to maintain a single, clear point of accountability. That approach can definitely help avoid confusion. From my side, I’ve seen plenty of situations where the setup is different, especially in project management or…