| Anonymous | Login | Signup for a new account | 2013-06-17 23:40 EDT |  |
| Main | My View | View Issues | Change Log | Roadmap | Wiki | ManTweet | Repositories |
| View Issue Details [ Jump to Notes ] [ Wiki ] [ Related Changesets ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
| 0012096 | mantisbt | feature | public | 2010-06-19 00:31 | 2013-04-06 09:26 | ||||||||
| Reporter | dhx | ||||||||||||
| Assigned To | dhx | ||||||||||||
| Priority | normal | Severity | minor | Reproducibility | N/A | ||||||||
| Status | resolved | Resolution | fixed | ||||||||||
| Platform | OS | OS Version | |||||||||||
| Product Version | 1.2.2 | ||||||||||||
| Target Version | 1.3.x | Fixed in Version | 1.3.x | ||||||||||
| Summary | 0012096: On marking an issue as a duplicate add the reporter and handler to the monitor list of the destination bug | ||||||||||||
| Description | When an issue X is resolved as a duplicate of an existing issue Y, the monitor list from X is copied to and merged with Y. However the reporter and handler of the source issue are not copied unless they're on the monitor list. It'd be helpful if this behavior was changed so that the reporter and handler were added to the monitor list of the destination bug so they don't mistakenly become 'out-of-the-loop' on updates to the issue. | ||||||||||||
| Tags | 2.0.x check | ||||||||||||
| Attached Files | |||||||||||||
 Relationships |
||||||
|
||||||
 Relationships |
|
Notes |
|
 (0036505)grangeway (developer) 2013-04-05 17:57 |
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|
Notes |
| Related Changesets |
|||
|
MantisBT: master 4c791523
Timestamp: 2010-06-19 04:38:26 Author: dhx [ Details ] [ Diff ] |
Issue 0012096: Add reporter and handler to monitor list on duplicate When an issue X is resolved as a duplicate of an existing issue Y, the monitor list from X is copied to and merged with Y. However the reporter and handler of the source issue are not copied unless they're on the monitor list. This change ensures that the reporter and handler of the source issue are added to the monitor list on the destination issue. These users are thus less likely to become out-of-the-loop on an issue that is relevant to them. |
||
| mod - core/bug_api.php | [ Diff ] [ File ] | ||
| Related Changesets |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-06-19 00:31 | dhx | New Issue | |
| 2010-06-19 00:31 | dhx | Status | new => assigned |
| 2010-06-19 00:31 | dhx | Assigned To | => dhx |
| 2010-06-22 21:40 | dhx | Changeset attached | => MantisBT master 4c791523 |
| 2010-06-22 22:52 | dhx | Target Version | 1.2.2 => 1.3.x |
| 2010-06-22 22:52 | dhx | Status | assigned => resolved |
| 2010-06-22 22:52 | dhx | Fixed in Version | => 1.3.x |
| 2010-06-22 22:52 | dhx | Resolution | open => fixed |
| 2013-04-05 17:57 | grangeway | Status | resolved => acknowledged |
| 2013-04-05 17:57 | grangeway | Note Added: 0036505 | |
| 2013-04-05 18:02 | grangeway | Relationship added | child of 0015721 |
| 2013-04-06 03:44 | dregad | Status | acknowledged => resolved |
| 2013-04-06 07:20 | grangeway | Status | resolved => acknowledged |
| 2013-04-06 09:26 | dregad | Tag Attached: 2.0.x check | |
| 2013-04-06 09:26 | dregad | Status | acknowledged => resolved |
|
Issue History |
| MantisBT 1.2.16dev master-1.2.x-05091f5 [^]
Copyright © 2000 - 2013 MantisBT Team
Time: 0.0915 seconds. memory usage: 2,816 KB |
|