Let's just cut this short, it's getting tedious.

The only reason I posted the script is that I resolved an issue for myself and passed it on to others in case it's useful.
It's not a mantis patch, it's mantis related. If you don't like it, delete it, if you do, use it.

That's all, nothing more, nothing less.

Michiel

Michiel Dethmers wrote:

I beg to differ. The audit trail is a pain in email, it's the entire reason I have and use mantis, as the audit trail of notes is recorded there, and not in my inbox. I only keep messages in my inbox that require dealing with as a reminder that something needs to happen, but I only need one reminder per issue. The issues I receive emails about are the ones that I am involved with, ie as project manager, developer, reporter or simply because I monitor the issue, so whatever settings I create, I will always receive multiple emails per issue. I guess it's mostly because my company is small and I do just about anything that needs doing, instead of passing it on to someone else in my company. But even then, just because you got involved with an issue, you will continue to receive emails about it.

Now tell me what the audit trail is of an inbox that looks like

[proj 3235] issue subject, date x
[proj 3235] issue subject, date y
[proj 3235] issue subject, date z

Michiel

David A. Desrosiers wrote:
I end up with at least 4 messages from Mantis in my inbox about the 
same issue. I go and work my way through my inbox and click delete 
for every one but the last for every issue. That is very tedious and 
something I can automate.
    

	Sorry, but those aren't "duplicate" messages. Its called an 
audit trail. I very much prefer it that way, so I can go back through 
emails and show developers (or users) what changed, even if the web 
side of things doesn't accurately reflect that change (such as when/if 
the db crashes and has to be restored from a backup).

	Why not configure Mantis properly so you don't receive the 
extra emails for everything except the New Bug creation events? Its 
all there in the config. Or are you still running with the defaults?

  
That's what the script does.
    

	Ok, so not much use to the majority of production Mantis 
installs then.


David A. Desrosiers
desrod@gnu-designs.com
http://gnu-designs.com


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Mantisbt-dev mailing list
Mantisbt-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
  

-- 

least likely to say "it can't be done"
most  likely to say "if it's not in mantis, it won't be done"

t | i | n | c | a | n || l | t | d

         Buenos Aires | London | Machynlleth

t | i | n | c | a | n || l | t | d 
  

-- 

least likely to say "it can't be done"
most  likely to say "if it's not in mantis, it won't be done"

t | i | n | c | a | n || l | t | d

         Buenos Aires | London | Machynlleth

t | i | n | c | a | n || l | t | d