Martijn Laarman's dashboard

That's OK Sarat, I'll reopen it when I can properly reproduce it.

True, but hacking up production code is stretching my love a tad too far even as low-risk-estimate as style changes are :) – Martijn Laarman, on April 27, 2009 09:12

True but this is often overlooked, which in turn is our (consumers) fault for not being educated enough i suppose. The need for automated emails stems more from a lack of overview in Fixx. I've posted several issues i have with the Dashboard that prevent me from using it as a place where i can f5 on to see what i missed.

- Dashboard shouldn't be grouped in my opinion but only sorted descending on date. The grouping often leads to overlooking changes in other projects and only seeing the last 5 changes per group has gotten me in trouble before (entirely my fault i know!).
- Dashboard doesn't show newly created issues (1.7)

I agree, i much rather force myself to go the fixx's index to see what's up. We can force ourselves to do so but our clients wont check back to see new comments regularly. A different set of rules should apply in my opinion for non users of fixx. They should get an email for every change in issues they've started or commented in.

Another note i want to raise is that while i think keeping the email messages to a bare minimum out of the box is a great thing however i do feel Fixx could greatly be improved with project based settings so we can enforce our own business rules when we see fit.

think:

- Notify all users of issue updates they're active in.
- Notify project lead (of everything)
- Global project watch.

Sometimes projects are that critical you need to act quickly, and as a developer i rather use my issue tracker as a means of communication in these cases. If i don't respond quickly testers,managers and clients will resort to different means of communication to get my attention and we all read enough joelonsoftware to know thats a bad thing :)

Loving this as well, agree with sebastiaan that hacking feels a bit dirty though.

I'd also love to see an email to all involved parties (assignee, project lead, issue submitter, anyone who commented). A bit like how getsatisfaction works if it wasnt for the emails i'd miss alot of good comments. Issue tracking is often critical and we rather get too much then too few emails, that might be us though.

I second Sebastiaan's suggestion, quite often checkboxes are overlooked this gives Fixx admin's a chance to set a guideline for an area :)

Good news Sarat, this will suit our needs just as well :)

On point 4 i can say we had a discussion on this several times for applications we built and it's still unsettled, camp 1 want latest at the top camp 2 latest at the bottom there's no pleasing everyone going one way. Making it a user derived setting would be awesome for all :)

hehe no problem glad to hear it will be solved ASAP :)