View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0010077 | mantisbt | preferences | public | 2009-01-23 11:41 | 2010-04-23 23:22 |
Reporter | NightThief | Assigned To | vboctor | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | duplicate | ||
Product Version | 1.2.0a3 | ||||
Summary | 0010077: Make changing update time with issue monitoring optional | ||||
Description | Please make change in http://www.mantisbt.org/bugs/view.php?id=9348 optional / configurable. Right now it can be considered like a bump in forums terminology. | ||||
Tags | No tags attached. | ||||
duplicate of | 0010857 | acknowledged | do not adjust "last updated" when monitor added |
You have the same behaviour every time you touch the bug in other ways, for instance adding a note, which is exactly like a bump. |
|
Well, notes are different. Probably I gave bad example. Better one would be following a topic in forum. Nobody really cares about that. |
|
Why would you want to monitor a closed report? In fact - I think i'd probably consider that to be a bug. In theory, CLOSE'd is the last state that a bug will enter and unless it is reopened ( i assume quite unlikely normally), you'd be monitoring something that will never change... |
|
Bump! --- I think it is useful to get a bump when someone monitors an issue, this is because there is interest in this issue and it is worth surfacing to the top. However, I wonder if it is worth the bump if someone unmonitor the issue (except for consistency). On the other hand, I wonder what you see as the disadvantage of this ON? Is there a certain behavior that causes this to be perceived as a negative thing in your environment? |
|
Hi, And here is an example when a user monitors closed report: http://bugs.miranda-im.org/view.php?id=59 Thank you for bumping this report :) |
|