Feature #3197


Added by Ewan Makepeace over 13 years ago. Updated over 9 years ago.

Status:NewStart date:2009-04-17
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


I really need a better way to track when issues last changed state. We have dates for Created and Updated - but in many cases an issue may be modified multiple times without progressing. For example at the end of each month all tasks that are assigned get updated to the new sprint month. People may also add comments or reassign tasks around the team - handing them back and forth. What I need to know is which tasks have not materially progressed the longest.
Another use is knowing for sure when tasks were closed (if they are closed). You generally assume that there have been no updates since a task was closed, but sometimes I find myself cleaning up categories, or making other changes that affect old closed tasks, and all their updated dates change. This breaks my statistics and spoils the integrity of Redmine as an issue database, as well as making my reports innaccurate.

What I would like is an additional field 'DateStatusChanged' which is updated every time an issue changes state and not otherwise.


#1 Updated by Dipan Mehta over 9 years ago

+1. Ideally, if we have 'tab' type view on the issues notes, it would be great to have 1 tab that explains the timeline wise flow of the ticket much the same way the Activity page provides the view in temporal way.

#2 Updated by Daniel Felix over 9 years ago

Yes I would agree that this is a good thing. But there should be the tabbed view first. ;-)

Also available in: Atom PDF