Hi I am Ramya. I am new to JIRA. Please advise me how to assign an issue to multiple assignees.
Hello,
You cannot assign one issue to multiple assignees. It is an impossible thing to do in Jira. Because this is against the principle of how Jira operates. If you assign one issue to multiple people, the responsibility of the issue will be vague and not clear. That's why you cannot do it.
However if it's very crucial, you can create optional configurations. For example, you can create a mail group that consists a group of people, create a user with this mail group on Jira and assign the issue to this user. But I would not recommend such a thing because of the reason I explained above.
If you explain the business reason why you want this, maybe we can find another solution that would fit your needs.
Regards.
Hi @Ramya Pendem
@Elifcan Cakmak is totally right, this is a thing against Jira's principles.
Work instead with watchers or if working with Jira Service Desk with request participants.
CheersNiklas
As a tester I assign an issue to the developer and I would like to send the status of the issue to my TL and PM also as a notification.Please suggest.
Regards,
Ramya
Hi,
As @Sloan N_ B_ suggested below, you can use watchers feature of Jira. Check out this blog post about watchers and mentions. If you want your TL and PM to get notification every time the issue is updated you can use watchers. If you want them to get one time notification you can use mentions.
https://www.atlassian.com/blog/jira-software/using-watchers-and-mentions-effectively
Other than that you can create issue filters for more than one issue and other people can subscribe to these filters to get timely notifications that you manage.
https://confluence.atlassian.com/jira064/receiving-search-results-via-email-720416706.html
Thank you for your support.
I am not able to understand from the above information.Could you please explain me step by step how to create watchers .
Has there been any movement on this? The participants and watchers are great if you are keeping an eye on certain issues. However, sometimes multiple tecnicians work together on the same project/task and it takes several hours to complete-- this only allows time credit due to one technician for that task.
If anyone else is also concerned about this-- I have suggested the techs to link tickets to the original request in order to record their time working on an issue. Of course, this woudl only apply to longer projects.
However, it would be great to have multiple assignees as an option so that the "Linked" tickets don't bring up the ticket count.
Thank you
There is no movement to be made - you do not want multiple-assignees and Atlassian are not going to implement it, they closed all the requests with "won't do".
What Nic said, when you assign a ticket to a technician that person becomes responsible for it (open to close) which is the principle that is reinforced in JIRA. If you have someone helping them, you could create a sub-task of that main ticket and assign that to the helper and put all their work/time on that sub-task which stays under the main task.
This entire argument neglects the fact that pair programming is a widely spread practice and JIRA basically becomes useless in tracking the pair currently working on a ticket. I hope Atlassian reconsiders their 20th century opinion on this topic
The ability to assign multiple task owners should be added to Jira, agile scrum at a minimum.
Collaboration is enshrined in both the agile manifesto and scrum guide and part of the DNA.. shared understanding, shared ownership, the best ideas come from developers and the business people working together daily, and the list goes on.
Shared ownership is a good thing! Beyond the active build stage, shared ownership can also be seen as shared recognition when a piece launches.
This would also enable stakeholders to have contingency or backup for a POC or if the previous task lead left the company.
In other applications where scrum is used for example Creative, it would be very beneficial for a landing page for eg. to be lead by both a writer and a designer. It feels like Jira is pushing a hierarchical approach.
Gotta respect the core agile principles and values if you expect people to use a product that labels itself "agile" & "scrum" prominently.
If it fundamentally or theoretically contradicts with something, why not just add it as an a settings toggle? There are settings for a million other things in there already!
I think you've completely missed the point here.
This sentence says it all: "In other applications where scrum is used for example Creative, it would be very beneficial for a landing page for eg. to be lead by both a writer and a designer."
Scrum says nothing about assignee, in fact, in your example, it directly says that you should not have a story that is "lead by a writer and a designer". The story is the responsibility of the development team. Not one or many individuals within it, the team is responsible. (And you know who the team is because the issue is in their backlog or on their sprint board)
@[deleted]why would Jira agile scrum have assignees at all then? In your thinking, each ticket would just be assigned to "Team" and this is absolutely not the case. Jira offers assignees, but only one.
There's tactical value in having multiple assignees noted in my original comment and fundamentally, you and jira overlook the tactical value owning something together.
This feature would foster better teamwork, especially in the more work-from-home world we now live in.
And remember, scrum is getting more widely used (applied) across various industries. If Atlassian expects its software will stand the test of time over the long-term then it should inspect and adapt based on what customers are asking for. That also is a key piece Atlassian is overlooking here - Give value to your customers, not your internal, theoretical, software-only myopic view holders.
You're right, Scrum doesn't need assignees at all, and we often find (healthy) scrum teams drop the field.
Jira offers a single assignee by design, and has done for a long time before any boards for supporting Scrum and Kanban were implemented in it.
It is designed that way because you should never never have multiple assignees. In all industries, in real life, multiple assignee does not work.
I've spent years sorting out the messes made by people implementing mulltiple assignees, and in some cases, this has been done by migrating away from systems that allow it on to more sane systems (including Jira) that explicitly do not allow it.
It looks like you're new here. Sign in or register to get started.
