We've migrated from Bugzilla (with millions of "bugs") to JIRA. In our Bugzilla instance, we let mailing list quasi-users own bugs, and that nominally meant that a subscriber would fix it. The entire mailing list would get notified when bug activity occurred.
We're trying for a new paradigm with our JIRA instance that issues should be assigned only to humans and that the proper assignee is the person who is responsible to see that the issue is resolved. The primary motivation is to encourage accountability. If an issue is assigned to a mailing list, how does anyone know that anyone is actually subscribed to it or that anyone pays any attention to list traffic? If entreaties to the mailing list fall on inattentive subscribers, what then? Human assignees have managers, and reporters can ping those managers if issues are given short shrift.
So much pushback! I'm getting besieged with terribly convoluted use cases that involve assigning issues to mailing list quasi-users to implement some process. Bugzilla doesn't have Service Desk or activity stream dashboards, so I can understand and sympathize with how those crazy processes came to be. However, there are some people who are terribly resistant to using the new capabilities that come with JIRA.
So far, I've been arguing on two fronts: the philosophical front of why it's not a good idea and how to use JIRA's capabilities to achieve some end, but I could use some more good points on both.
Thanks for reading!
Also, it may be a good point to ask "why would assign to a mail list do us good" in the first place?
If needed, you can find some mid-ground as in How do I assign issues to multiple users.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG