View Issue Details

IDProjectCategoryView StatusLast Update
0010857mantisbtotherpublic2017-09-12 04:20
ReportercasAssigned To 
PrioritynormalSeveritytweakReproducibilityN/A
Status acknowledgedResolutionopen 
Product Version 
Target VersionFixed in Version 
Summary0010857: do not adjust "last updated" when monitor added
Description

When someone starts monitoring an issue, also the "last updated" field is updated. Although i do support the changelog being updated, i believe that it does not justify to update the "last updated" field since nothing really happened to the issue.

TagsNo tags attached.

Relationships

has duplicate 0010077 closedvboctor Make changing update time with issue monitoring optional 
has duplicate 0023343 resolvedatrol Monitor/End Monitor should not change the "last modified" date 

Activities

vboctor

vboctor

2009-08-25 02:30

manager   ~0022807

The reason last updated is changed when a user monitors an issue is to reflect the continued interest in the issue and bubble the issue to the top, where developers would see it again. This is similar to a "ping!" feature.

However, I agree that this behavior could be made configurable.

Issue History

Date Modified Username Field Change
2009-08-21 03:10 cas New Issue
2009-08-25 02:30 vboctor Note Added: 0022807
2009-08-25 02:30 vboctor Status new => acknowledged
2009-10-10 01:58 vboctor Relationship added has duplicate 0010077
2017-09-12 04:20 atrol Relationship added has duplicate 0023343