Defect #5639

"Watching" a ticket doesn't update ticket

Added by James Turnbull about 9 years ago. Updated almost 9 years ago.

Status:ClosedStart date:2010-06-03
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution:Cant reproduce Affected version:


This is how my workflow works generally:

  • see interesting bug via mail
  • open bug link
  • click watch
  • go to update bug
  • "the bug has been updated by someone" error

The problem appears to be that when you hit 'watch', it doesn't refresh the page, so when you hit an update, it considers the watch change to have happened behind your back.


#1 Updated by Felix Schäfer about 9 years ago

Mmh, I think I've been doing what you are describing for a long time without having any problem. Trying just now, if you can read this, I wasn't able to reproduce here :-)

Some more detail about your setup? (see SubmittingBugs)

#2 Updated by James Turnbull about 9 years ago

A user downstream reported it us. We're using Redmine trunk - pretty close to HEAD.

About your application's environment
Ruby version              1.8.7 (x86_64-linux)
RubyGems version          1.3.5
Rack version              1.0
Rails version             2.3.5
Active Record version     2.3.5
Active Resource version   2.3.5
Action Mailer version     2.3.5
Active Support version    2.3.5
Environment               production
Database adapter          mysql
Database schema version   20100429224143

About your Redmine plugins
Redmine Vote plugin        0.0.2
Google Analytics plugin    0.1.0
Markdown Extra formatter   0.0.2
Bots filter                1.02
Redmine Simple Support     0.1.0
Redmine Hudson plugin
Markdown formatter         0.0.1

#3 Updated by Felix Schäfer about 9 years ago

Just tried with JS off to see if that could be the cause of the problem, but that doesn't cause the error you mentioned.

Can your user reproduce it, and if yes, could you capture the log snippet pertaining to that?

#4 Updated by Felix Schäfer almost 9 years ago

James, have you eben able to reproduce this in any menaningful way, or to find some error log or trace?

#5 Updated by James Turnbull almost 9 years ago

  • Status changed from New to Resolved

I can't replicate this. I suspect it's a browser issue. Closing.

#6 Updated by Felix Schäfer almost 9 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Cant reproduce

Thanks for the feedback!

Also available in: Atom PDF