View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0016556Mylyn ConnectorGeneralpublic2013-10-31 07:322013-11-22 08:52
Reportermpol Assigned Torombert  
PrioritynormalSeverityminorReproducibilityhave not tried
Status feedbackResolutionopen 
Product Version3.9.0 
Summary0016556: Updating a monitored issue results in spurious monitor change emails
Description

When an issue is updated which has monitoring users, they are first unsubscribed from the issue and then readded to it. And they apparently receive two emails about this effectively null change.

TagsNo tags attached.

Activities

rombert

rombert

2013-10-31 07:55

manager   ~0038398

Thanks for the report. What version of MantisBT are you using? I think this is something controlled by the SOAP API.
mpol

mpol

2013-10-31 08:15

reporter   ~0038399

Well, this is 1.2.10 with the patch for 0014558 applied by the administrator.

And indeed I see that the description of 0014558 explicitly mentions deleting and readding monitors.
mpol

mpol

2013-11-14 08:45

reporter   ~0038554

When the problem happened the issue was being unassigned, so the fields that legitimately changed were:

  • assigned to - from someone to noone
  • status - from assigned to new

And apart from that: description is recorded as updated (without a real change - I thought I remember such issue being reported, but I cannot find it) and the monitor was removed and readded.

When just adding a comment to a monitored issue a moment ago I did not experience any additional unexpected changes.
rombert

rombert

2013-11-22 08:52

manager   ~0038627

This is definitely part of the SOAP API, not of the connector, but keeping it in here until I determine the root cause.

The behaviour you report is inconsistent with the current code though. You report that users are removed and then added back to the monitor list, whereas the code first adds new monitors and then removes those which should no longer monitor the issue. As such I'm going to ask you to re-test with MantisBT 1.2.15 and report back if the problem still exists.

Also, if you still get the incorrect description history event after upgrading, file a separate bug.

Thanks!