Well, you did a nice job of preventing workflow updates from updating the update date, but one case was either missed or deliberately handled in a different way.

When migrating issues from one workflow to another, sometimes the status has to be re-mapped. For example, I improved my workflow to get rid of the Re-opened status, so 9 issues had to change from Re-opened to Open. In the change history, there is one entry for the workflow and status change, and the date has been updated.

I can see the logic in doing so, but if you think about it, this really isn't a transition in the strict sense of workflows - it's an administrative change that does not reflect anyone touching the issue. So now, I have some issues that haven't been touched in months showing up on my most recently updated filter. Ugly. I can see this as being a gray area between bug and improvement, but IMHO it should not behave this way.

By the way, changing workflow only took about 3 minutes on 3.6.5 Tomcat 5.5 instead of about 1.5 hours (if it completed at all) on 3.6.3 Weblogic.

P.S. I noticed you renamed the Test project to "A Test project" so it would come up first alphabetically. Try renaming it to " Test Project" where there is a blank in the first character - that does the same thing