Issue with mass resolve function

I am facing a minor, but definetely annoying (at least for
me), issue
with the mass resolve function.

Short background: I have a CVS_HEAD version in all my
projects. During
development, when bugs are resolved they are marked resolved
in
CVS_HEAD. When a release happens, all bugs resolved in
CVS_HEAD are
moved to the new version.

The issue is that the mass resolve feature won't let me
change the
"Fixed in version field" because the bug was
already in the "Resolved"
state; the relevant code (v1.0.6) is in bug_actiongroup.php
where
(AFAICT) something like the following is done (actual code
in
http://pastebin.co.uk/120
39 ):

if ( ( user has proper access ) &&
    ( current status < resolved ) &&
    ( workflow allows transition )
   )
{
    resolve bug
}

Now, it seems to me that the second condition could be
safely removed,
since the transition is explicitly checked in the last
condition, so
that it will be possible to mass change
"Resolution" and "Fixed in
version" fields regardless of the current bug status.

opinions?

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
mantisbt-dev mailing list
mantisbt-devlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-d
ev

Is there a reason why you are not using the group action
"Update Fixed
in Version" to do this?  Having transitions from
resolved to resolved
in the work flow would make it confusing.

On 3/20/07, Gianluca Sforna <giallugmail.com> wrote:
> I am facing a minor, but definetely annoying (at least
for me), issue
> with the mass resolve function.
>
> Short background: I have a CVS_HEAD version in all my
projects. During
> development, when bugs are resolved they are marked
resolved in
> CVS_HEAD. When a release happens, all bugs resolved in
CVS_HEAD are
> moved to the new version.
>
> The issue is that the mass resolve feature won't let me
change the
> "Fixed in version field" because the bug was
already in the "Resolved"
> state; the relevant code (v1.0.6) is in
bug_actiongroup.php where
> (AFAICT) something like the following is done (actual
code in
> http://pastebin.co.uk/120
39 ):
>
> if ( ( user has proper access ) &&
>     ( current status < resolved ) &&
>     ( workflow allows transition )
>    )
> {
>     resolve bug
> }
>
> Now, it seems to me that the second condition could be
safely removed,
> since the transition is explicitly checked in the last
condition, so
> that it will be possible to mass change
"Resolution" and "Fixed in
> version" fields regardless of the current bug
status.
>
> opinions?
>
>
------------------------------------------------------------
-------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the
chance to share your
> opinions on IT & business topics through brief
surveys-and earn cash
> http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> mantisbt-dev mailing list
> mantisbt-devlists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mantisbt-d
ev
>

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
mantisbt-dev mailing list
mantisbt-devlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-d
ev

On 3/20/07, Victor Boctor <vboctorgmail.com> wrote:
> Is there a reason why you are not using the group
action "Update Fixed
> in Version" to do this?

Because it's not there in 1.0.6 is enough for a reason? ;)

Seriously, I just realized what I needed is there in the 1.1
serie.
Would you consider the option of backporting to 1.0.x this
feature?

> Having transitions from resolved to resolved
> in the work flow would make it confusing.

Agreed. thanks for the help

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
mantisbt-dev mailing list
mantisbt-devlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-d
ev

Hi Gianluca,

On 3/21/07, Gianluca Sforna <giallugmail.com> wrote:
> On 3/20/07, Victor Boctor <vboctorgmail.com> wrote:
> > Is there a reason why you are not using the group
action "Update Fixed
> > in Version" to do this?
>
> Because it's not there in 1.0.6 is enough for a reason?
;)
>
> Seriously, I just realized what I needed is there in
the 1.1 serie.
> Would you consider the option of backporting to 1.0.x
this feature?

I don't think it meets the bar.

Regards,
Victor.

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
mantisbt-dev mailing list
mantisbt-devlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-d
ev