From: David Hicks <hickseydr@op...> - 2010-03-04 08:11:27
On Tue, 2010-03-02 at 13:22 -0600, Fetzik, John wrote:
> I am not particularly familiar with the code, but I took a look at the
> code and noticed a change in bug_update.php that might explain this
> behavior. Starting around line 160 of bug_update.php it looks like if
> the new status is equal to or greater then Resolved, but less then
> Closed it calls bug_resolve. The bug_resolve function explicitly sets
> the status of the bug to bug_resolved_status_threshold instead of the
> new status value that the user selected. In our case Staging.
I made this change in commit 5cd754dac3fe8832e8006b792a0d75cfef21f4eb.
> So my questions is, is this the intended behavior? I understand why
> the bug_resolve function is called, but should it be forcing the
> status to bug_resolved_status_threshold, which by default is Resolved.
The behaviour you're experiencing wasn't intended. The bug_resolve
function needs to accept a parameter for the status to which the bug is
being resolved. I'll see what I can do to fix this problem.
Thanks for reporting this issue!
Get latest updates about Open Source Projects, Conferences and News.