Austin Group Defect Tracker

Aardvark Mark III

Main | My View | View Issues | Change Log | Docs
  

Viewing Issue Simple Details [ Jump to Notes ] [ Issue History ] [ Print ]
ID Category Severity Type Date Submitted Last Update
0000115 [Aardvark Bugs] Aardvark Mk III Comment Enhancement Request 2009-07-01 20:10 2009-07-18 02:05
Reporter markh View Status public  
Assigned To msbrown
Priority normal Resolution Accepted  
Status Closed  
Name Mark Harris
Organization
User Reference
Summary 0000115: Email notifications do not report what was updated
Description The automatic email notifications that are sent to the Austin group list for issue updates include the entire issue description and all notes, but do not report what was updated. There is a link in the email, and it is possible to follow the link, scroll down to the issue history, and look for the actions with today's date. For example it might show that the field "Organization" was changed to "Self". However it would be nice if that was reported in the email.
Desired Action Change the email notification to report what was updated. Preferably the description and notes would not be included except when added or updated.
Tags No tags attached.
Attached Files

- Relationships

-  Notes
(0000154)
msbrown (manager)
2009-07-06 14:19

 [via Don Cragun]
I know I'm dreaming here, but what I would really like to see in the
update e-mails is the following:
1. A link to the bug in Mantis: So I can quickly skip to the full bug
     report if I want to look at the whole thing.
2. Summary: This field is short and gives me a brief idea of the
     subject matter
3. Issue History: only the final entries that have the Date Modified
     value corresponding to the change that generated this e-mail.
4. Project, Category, Type, Severity, Priority, & Status: iff the field
     isn't in the Issue History. Issue ID is not needed since it is
     obvious from the link to the bug in Mantis.
5. Date Submitted: so I have an idea of how long the bug has been
     around. Last Modified is not needed since the time stamp on the
     Issue History entry tells me what I need to know here.
6. The contents of any new or changed fields, but only if the change is
     not already visible in the Issue History.

I'm not sure about the Description and Desired Action fields. They give
a lot of context, but they can be huge. (#6 above obviously overrides
this if either of these fields changes.)
(0000162)
msbrown (manager)
2009-07-16 21:10

 OK, I've added back Issue History, but "don't resend the entire text of the bug" is going to take more work; stay tuned.
(0000163)
msbrown (manager)
2009-07-17 21:31

 Now let us see if this reduces the text when a new note is added to a bug.
(0000164)
msbrown (manager)
2009-07-17 21:47

 This should be the last, and only, bugnote shown.
(0000165)
msbrown (manager)
2009-07-18 01:44

 Due to an unfortunate php error my my part, trying to make this the last note shown.
(0000166)
msbrown (manager)
2009-07-18 02:05

 Email notifications should now be less verbose.
You will only see the whole Description/Action text upon first opening the bug.
You will only see the bugnotes when they are added (just the new one).
The change history will always be in the note, so you can see exactly what has changed.

Bugzilla does this part better than Mantis, I'll admit.

- Issue History
Date Modified Username Field Change
2009-07-01 20:10 markh New Issue
2009-07-01 20:10 markh Name => Mark Harris
2009-07-02 19:22 msbrown Assigned To => msbrown
2009-07-02 19:22 msbrown Status New => Under Review
2009-07-06 14:19 msbrown Note Added: 0000154
2009-07-16 21:10 msbrown Note Added: 0000162
2009-07-17 21:31 msbrown Note Added: 0000163
2009-07-17 21:47 msbrown Note Added: 0000164
2009-07-18 01:44 msbrown Note Added: 0000165
2009-07-18 02:05 msbrown Note Added: 0000166
2009-07-18 02:05 msbrown Status Under Review => Closed
2009-07-18 02:05 msbrown Resolution Open => Accepted

Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker