View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001241 | mantisbt | bugtracker | public | 2001-11-28 15:15 | 2003-12-13 04:48 |
Reporter | prescience | Assigned To | vboctor | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Summary | 0001241: Consider a CC: bugzilla type field | ||||
Description | This would be to keep others involved in your bug. This might make up for having only one handler at one time on a bug. Keep others who are involved in your work (maybe project managers etc.) abreast of what is happening and invite developer comments and feedback. | ||||
Tags | No tags attached. | ||||
Please do not add this field! Again, see my comment on 0001144. I'd rather vote for a "watchers" feature. |
|
can we close this bug since we now have the "monitor bug" feature? |
|
I think the current monitor feature does not cover the benefits of a cc field. The reason is that a user can not make another user monitor a bug. This feature can be satisfied by allowing user to multiple select users to monitor a given bug (or may select one at a time, although this won't be my preferred option). Is the aim to cc only registered users? or any e-mail address or allowing both depending on a config? Of course overloading Monitor feature can only achieve cc'ing of registered users. As for the benefit of such feature, it is very useful when reporting a bug or handling a bug, and you want to involve your manager, the responsible test engineers, support person, documentation, ...etc. Having such feature will give the reporter/handler the flexibility to notify people based on the contents of the bug. Also note that this requirement will not be satisfied by the custom fields feature. |
|
See 0002226 which was marked as duplicate for this one. |
|
This feature is now achievable through the reminders feature. See the following configuration options for more details: $g_bug_reminder_threshold |
|