View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000026 | Aardvark Bugs | public | 2009-05-15 13:50 | 2009-06-14 16:03 | |
| Reporter | msbrown | Assigned To | msbrown | ||
| Priority | normal | Severity | Objection | Type | Omission |
| Status | Closed | Resolution | Accepted | ||
| Name | Mark Brown | ||||
| Organization | IBM | ||||
| User Reference | |||||
| Summary | 0000026: need to be able to get all email for all projects | ||||
| Description | Don Cragun: >> There also needs to be a way for a user to say "Send me email for all >> updates to all bugs." at least for each product. I haven't found where >> I can set that up yet. > > Hopefully you mean, "all changes to bugs I opened or am monitoring" > and not "all bugs in the project". As an OR, I feel it is my responsibility to keep up-to-date on the status of aardvark (or Mantis) requests. I used to be able to subscribe to a couple of Austin Group aliases and attend the meetings to follow all of the discussions. Adding a step of having to login to Mantis and manually update each new report to list myself as someone monitoring the bug seems like it will waste a lot of my time. | ||||
| Desired Action | allow for this in preferences somehow, or to AGMailList | ||||
| Tags | No tags attached. | ||||
|
|
I have made the corrections to the configurations that I think will work. the AGMailList user (whose email address now points to a private addr, but will point to the main Austin Review list) now will get email on every status change or note addition to every defect in the "public" projects (Issue 6, Issue 7, Aardvark Bugs). In this way, you will not have to monitor every bug. |
|
|
see note above. |
|
|
I've applied this solution and tested it internally. I appears to work (I still have the "mail list" set to a private address). If you see this note, please respond with a note so I will know this part of the system works (submitter also sees notification of change). |
|
|
Closing this one out. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-05-15 13:50 | msbrown | New Issue | |
| 2009-05-15 13:50 | msbrown | Name | => Mark Brown |
| 2009-05-15 13:50 | msbrown | Organization | => IBM |
| 2009-06-07 14:09 | msbrown | Note Added: 0000032 | |
| 2009-06-07 14:09 | msbrown | Status | New => Under Review |
| 2009-06-07 14:09 | msbrown | Assigned To | => msbrown |
| 2009-06-07 14:09 | msbrown | Note Added: 0000033 | |
| 2009-06-07 14:09 | msbrown | Status | Under Review => Applied |
| 2009-06-07 14:09 | msbrown | Resolution | Open => Accepted |
| 2009-06-07 16:03 | msbrown | Status | Applied => Resolved |
| 2009-06-14 15:39 | msbrown | Note Added: 0000044 | |
| 2009-06-14 15:39 | msbrown | Status | Resolved => Applied |
| 2009-06-14 16:03 | msbrown | Note Added: 0000046 | |
| 2009-06-14 16:03 | msbrown | Status | Applied => Closed |