Loading Profile...
CC More People About a Bug/Issue
i'm not sure about this one, but it came up a few times so far:
all bugs have asignees, but we can't CC more people into a bug's status. we thought about creating a few mailing lists for each part of the team, but that needs maintenance, the exact reason why we choose ASP software for this. ultimately, we are looking for something like how you can copy people into messages in basecamp, and how they can remove themselves. i imagine that's a lot, just being able to CC more people on the bug report and have them follow it until the end could probably be enough.
all bugs have asignees, but we can't CC more people into a bug's status. we thought about creating a few mailing lists for each part of the team, but that needs maintenance, the exact reason why we choose ASP software for this. ultimately, we are looking for something like how you can copy people into messages in basecamp, and how they can remove themselves. i imagine that's a lot, just being able to CC more people on the bug report and have them follow it until the end could probably be enough.
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has not planned to implement this.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?This is something that's kind of on our radar. We definitely want to enable people to subscribe/unsubscribe themselves, but right now, we're not too keen on enabling a CC function like Basecamp has.
The reason we've chosen not to support this is two-fold. First and foremost, we feel that makes it too easy to arbitrarily include people that don't necessarily need to be involved. As a result, some people may begin to ignore the notifications. However, if we only send emails to people who are directly involved (the assignee, the opener, or someone who has commented) then they can be more confident that every notification is relevant. The way we see it, it's ultimately up to the assignee to pull other people into the conversation as needed, and then they become the most accountable person for the evolution of an issue.
Second, and still pretty important, is that it makes the issue submission form more complicated. While this is only one bit of functionality, it can lead to a significant number of options for creating an issue. Naturally, there are several other requests for additional fields/options, and it's a very slippery slope.
So, while we're thinking about enhancing the follow/unfollow capabilities, it's unlikely that we'd add checkboxes for CC'ing people.
I’m optimistic that we'll find a good compromise
The company thinks
this is one of the best points
-
Inappropriate?maybe one way could be to add a "follow" link on issues, so interested people can start following the issue, it isn't completely evident that commenting an issue will CC you into that bug1 Comment Add a comment
This is one of the best points
-
Yeah, right now that's the most likely execution. It was actually a feature that I had originally designed, but I wanted to see if we could hold off on adding it. Hopefully it will make its way into Sifter in the next couple of months.
EMPLOYEE
