FS#13224 - When reopening a bug, the comment gets the wrong date

Attached to Project: Arch Linux
Opened by Keld Simonsen (keld) - Thursday, 12 February 2009, 07:33 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 08 June 2009, 22:37 GMT
Task Type Bug Report
Category Bugtracker
Status Closed
Assigned To Roman Kyrylych (Romashka)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I requested reopening of http://bugs.archlinux.org/task/12240#comment39267
over a month ago. But it turned up just yesterday, wed 11. feb 2009, with the date of yesterday as the comment submission date. Naturally the fixers were confused, as the problem was resolved automagically in the meantime.

My own conclusion: do not reopen a bug, rather report a new bug, as reopening requires moderator intervention. My recommendation: remove reopening from web site functionality.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Monday, 08 June 2009, 22:37 GMT
Reason for closing:  Upstream
Additional comments about closing:  see the last comment
Comment by Greg (dolby) - Thursday, 12 February 2009, 11:17 GMT
The first issue is upstream. A FlySpray one.
As far as the second one, from my experience reopening bugs is needed in some occasions.
And its up to the moderator to open it, so i dont see a reason not having that.
What was done in  FS#12240  you link to was a mistake. They dont happen that often.
Comment by Jan de Groot (JGC) - Thursday, 12 February 2009, 11:45 GMT
Is there a possibility for developers to get a reopen notification when someone requests to reopen a bug? I can reopen bugs, but why don't I get a notification if someone requests a reopen for a bug that is assigned to me?
At this moment we're limited to the bugtracker team to reopen bugs. If they don't have time to work on the bugs, reopen requests can be stalled for over a month, resulting in these obsolete reopened bugs.
Comment by Gavin Bisesi (Daenyth) - Saturday, 21 March 2009, 14:56 GMT
Should this be reported upstream and closed? Anything we can do on our end?
Comment by Roman Kyrylych (Romashka) - Thursday, 28 May 2009, 18:28 GMT
Yet another of multiple flyspray bugs, didn't know about it though.
@JGC - hm, I thought devs get notifications about reopening because flyspray adds user's reopening request as a comment automatically.

Something has to be done with this flyspray bugs....
Assigning it to myself to not forget it.
Comment by Roman Kyrylych (Romashka) - Monday, 08 June 2009, 22:37 GMT
Flyspray was just updated. The problem still exist. See  FS#14596  - I reopened it just a minute ago and that's the date/time of comment, not when it was originally requested for reopening.
I'm not sure if this behaviour should be considered, but it's definetely should be reported and handled upstream. Closing this.

Loading...