Loading Profile...
[1.8] email notification improvements ?
I was wondering whether anything has changed regarding email notifications ? I CTRL+F 'ed for "email" on the changes list to no avail.
We (developers) really like to send out more emails to draw the attention of clients (and managers) who don't login to see bugs 10 times a day :) Right now I'm not certain a comment I make is going to get noticed and thus often resort to emailing the client myself notifying him that i need more input or that I've fixed bugs he's opened.
What would be really cool is if:
- Users can opt to listen to projects/area's getting email notifications of anything that happens. With some flood protection of course so that emails are only send every 10 minutes containing stuff that happened.
-When commenting have a checkbox that says "notify users related to this project". so that i can send a message to the client, assignee etc.
- Clients recieve a daily email of updates to issues they've opened. A sort of report of progress sort of speak. To clients such a feature is gold. ("Hey look they've fixed that annoying bug in the next version!")
I know my email heavy philosophy goes against your core being Sarat but having the option to turn Fixx into a as email heavy (or lean) system as you can personally tollerate would really add value imo.
We (developers) really like to send out more emails to draw the attention of clients (and managers) who don't login to see bugs 10 times a day :) Right now I'm not certain a comment I make is going to get noticed and thus often resort to emailing the client myself notifying him that i need more input or that I've fixed bugs he's opened.
What would be really cool is if:
- Users can opt to listen to projects/area's getting email notifications of anything that happens. With some flood protection of course so that emails are only send every 10 minutes containing stuff that happened.
-When commenting have a checkbox that says "notify users related to this project". so that i can send a message to the client, assignee etc.
- Clients recieve a daily email of updates to issues they've opened. A sort of report of progress sort of speak. To clients such a feature is gold. ("Hey look they've fixed that annoying bug in the next version!")
I know my email heavy philosophy goes against your core being Sarat but having the option to turn Fixx into a as email heavy (or lean) system as you can personally tollerate would really add value imo.
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Great idea.
I have to admit, the messaging system we've built into fixx definitely has its weaknesses.
This is one of those scenarios where by, we didn't want to blindly assume that emails where to be sent at every system change. At the same time we did not want to pollute the interface and complicate collaboration any further than what is already built into 1.8...
...however saying that... ...your ideas on 10 minute updates and flood protection are a great work around to this. Client opt in on projects/areas and daily email reports are also two things we've had in the pipe line but never had requests for so have been pushed to the back of the roadmap.
Although we do try to avoid this kind of disconnected communication i.e reliance on email i can see a clear benefit in the cases you've described, that being said the features you describe are exactly the kind of feedback we need to move forward and enhance not only the level of communication but also the level of productivity that fixx can provide.
thanks ;-)
I’m Excited about the level of features in this question
-
Inappropriate?Since Martijn mentioned my e-mail and spam ethos in the question, it is only right I pitch in with my 2 pence.
We have heard loud and clear from many of our clients about the improvements that can be made with e-mail interaction. By far the biggest requested feature is being able to send e-mails INTO fixx, which we aim to address for 2.0.
I agree that where e-mail really works (and fixx probably doesn't deliver the punch) is when you need to work with clients who refuse to use the web interace at all. They just want to get an e-mail and reply to it. Here is what I think the way forward should be,
- I love the idea of people "watching" a project so that they can get all updates for that project and are auto-subscribed to the watchers of each issue in that project. In that way, if you choose to not watch an issue, you can still keep auto-subscribe on for the entire project but un-subscribe from individual issues.
Flood protection is an interesting idea but will probaly need a lot more work and not something we can implement quickly.
- I like the idea of "Notify people related to this issue". I am a bit concerned that we are getting far too many notification options into fixx now and if it would have been better to just notify everybody at every change (the spammy way which I hate) rather than provide loads of notification options that duplicate the functionality everywhere.
- Daily progress reports are definitely in. I love the idea and we have been planning something like this for a while. To me, this would actually a summary of issues rather than detail of all the changes. So essentially a more functional version of the issue list but one which included only issues created by your and key info about them. This one is probably for 2.0
The company says
this answers the question
-
Inappropriate?Thanks for the excellent feedback guys. Perhaps a special email settings page in the administration tab could help remove unwanted clutter from the reporting page and thus minimize on duplicating functionality ? This way fixx could work the way it always has out of the box but could also satisfy spam heads like myself :)
1 Comment Add a comment
This answers the question
-
I agree that a lot of this can be moved to administration but there are a fair few bits which will need to be in-line with the action (like notify all related people). I am sure you will get more info on this as we work on it.
EMPLOYEE
EMPLOYEE
