More interesting bugs :)

https://drupal.org/comment/8135859#comment-8135859

That issue was marked as closed (fixed) manually almost two years ago. Now it was moved from *Fixed* (huh?) to closed (fixed) again.

The second problem is that I got an e-mail notification for it, something that didn't happen before.

The same happens for testbot updates, but that's something that I actually like, because it tells me that the test finished (and failed), which is useful information.

Comments

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Just got two more, #1974032: Make title of newsletter link to online version and #2081727: Add mollom captchas to public forms. The third looks like a valid close, only problem is the notification, the first is even weirder and was already auto-closed?

I suspect I'll get a few more of those over the next hours...

tvn’s picture

tvn commented
Status: Active » Postponed
Related issues: +#2125247: Email being sent for automatic issue updates, +#2125263: Issue status not taken from last comment during D7 migration

For notifications there is #2125247: Email being sent for automatic issue updates. Issues being closed again, I think the problem is here: #2125263: Issue status not taken from last comment during D7 migration. Issues probably got wrong statuses (fixed) post upgrade and got closed, since they were old. Not going to close this one as duplicate for now to let people find the other issues.

pdrake’s picture

pdrake commented

Not sure if this is the same bug, just with different circumstances, but I had an issue that was sent directly from RTBC to Closed with the "Automatically closed - issue fixed for 2 weeks with no activity." comment (without ever having been marked fixed): https://drupal.org/node/1808954

tr’s picture

tr commented

I can confirm the first part of the OPs issue report.
I have a couple of issues that were Closed (fixed) long ago receive new "System message" comments that moved them from Fixed -> Closed (fixed) again. For instance:

#2083933: Product fields ordering fails when nodes standard fields get weighted > 10
#1875466: Attribute "label" in add-to-cart form is "name"
#260496: Error all ubercart imagecache presets

(That last one is over 5 years old! Surprising to see it back at the top of the issue queue...)

jonathan1055’s picture

jonathan1055 commented

@pdrake, yes in #1808954: Use Block title as an option the timstamp for comment #3 was the latest time (because that comment got editted after #4 was added, by the looks of it). Hence, from what I have seen on other issues, during the upgrade the incorrect status of 'fixed' was taken from #3 even though it had been set to 'rtbc' in #4. This is the same bug as explained in #2125263: Issue status not taken from last comment during D7 migration. I think that issue is going to remain as the 'parent' for this problem.

Jonathan

jonathan1055’s picture

jonathan1055 commented
Status: Postponed » Closed (duplicate)

Closing this issue now, as both of the OPs problems are covered by other (earlier) open issues:
#2125247: Email being sent for automatic issue updates
#2125263: Issue status not taken from last comment during D7 migration

jonathan1055’s picture

jonathan1055 commented
Parent issue: » #2125263: Issue status not taken from last comment during D7 migration
Related issues: -#2125263: Issue status not taken from last comment during D7 migration