View Issue Details

IDProjectCategoryView StatusLast Update
0000955mantisbtfeaturepublic2014-10-02 18:21
ReporterrepAssigned Tograngeway  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionno change required 
Summary0000955: Group Email
Description

It would be good to add optional facility to send e-mails to the whole group.

TagsNo tags attached.

Activities

prescience

prescience

2001-09-26 09:00

reporter   ~0001361

I agree. I'm looking into the rules and options that emailing should have.

tomki

tomki

2001-09-27 01:06

reporter   ~0001371

One option that I was about to add a feature request for:
per-project assignable stale-bug reminder emails.
If that isn't clear: For project A the stalebug timeout is 2 days, it's high-priority. If a bug is open and not 'wontclose' or something, the owner and optionally the submitter get a reminder email to get on the ball.
Project B is lower priority, maybe the stalebug timeout is 5 days.

rcrespo

rcrespo

2002-06-27 19:53

reporter   ~0002917

I think this is a very good idea. Kind of remind developers to look at things if they aren't checking up on stuff.

jslarve

jslarve

2003-04-29 02:12

reporter   ~0004268

If anyone's still looking into the idea of (administrators) sending an e-mail to the whole group (if they have this "opt-in" checked in their preferences), I think it would be a great idea. Kinda like "news", but sending an opted-in (non-spam) e-mail.

gfroese

gfroese

2003-05-16 18:42

reporter   ~0004319

this might be better served if the timeout is set on a priority basis for each project rather than the whole project. no point in getting reminders for a trivial bug every two days. perhaps even making it definable for each bug is the answer.

brewthatistrue

brewthatistrue

2004-01-05 18:05

reporter   ~0004851

i also would like to be able to manually email users.
i have less than 100 users total with no signups and no anonymous users (i added them all myself).

some of them haven't ever logged in (they are in the "prune") list

if they don't want bugtracker access, i can delete them, but if they just don't know how to access it, then i want to make sure they know how.

grangeway

grangeway

2014-09-22 15:31

reporter   ~0041272

I'm resolving this issue as "no change required" - please do not hesitate to reopen the issue if you believe that this issue should still be looked into.

It would help if you could ensure that the issue still applies to the latest stable version of MantisBT which is available from the mantisbt.org website.

Having evaluated the description, notes on this issue and looking at the time it was actually submitted, I believe the sensible thing to do with this issue for now is to mark it as resolved, and then to reopen this issue if you feel it is still important enough dedicate some time to it.

I think before we'd be able to do something like this, we'd need to look at whether to add the concept of 'user groups' to mantis in a clear way. This could then be used to allow for some internal messaging system or emails.

In terms of "emailing anyone", i'm tempted to say that sort of functionality would be best implemented as a plugin as it avoids potential issues of being able to spam 20,000 people email if a bugtracker has 20k accounts in one go and we had some security vulnerability.

Whereas in the case of a plugin, the end user would have to make a definite choice about whether to install and enable such a plugin.

Thanks
Paul (paul@mantisforge.org)