re: bug assignment flow...

Hi mantis list,

When a bug/CR is assigned to a Developer and he/she marked
it as "Resolved" - The status is "resolved" and resolution
is "fixed". Which is all good and as expected. Now when we
have a new Build and the bug/CR is assigned back to QA,
it's keeping the resolution as "fixed" and changing the
status to "assigned". 

I want to keep the status as "resolved" how can I change
that assignment/process flow.

thanks 

		
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Re: re: bug assignment flow...

I am using a different approach, may be can be useful for you:
When a bug/CR is assigned to a Developer and he/she resolves:
status is setted to TESTED IN DEV.
We never assign bug to QA people.
When QA verifies that bug is really OK, they change status to RESOLVED.
The original reporter is the only people able to change status
to CLOSED.

does any sense for you ?

regards

Francisco

> it as "Resolved" - The status is "resolved" and resolution
> is "fixed". Which is all good and as expected. Now when we
> have a new Build and the bug/CR is assigned back to QA,
> it's keeping the resolution as "fixed" and changing the
> status to "assigned". 
> 
> I want to keep the status as "resolved" how can I change
> that assignment/process flow.
> 

-----Original Message-----
From: Roy Sin <roy_sin@...>
To: mantisbt-help@...
Date: Wed, 7 Dec 2005 14:44:04 -0800 (PST)
Subject: [Mantisbt-help] re: bug assignment flow...

RE: re: bug assignment flow...

Hi Roy,

> When a bug/CR is assigned to a Developer and he/she marked
> it as "Resolved" - The status is "resolved" and resolution
> is "fixed". Which is all good and as expected. Now when we
> have a new Build and the bug/CR is assigned back to QA,
> it's keeping the resolution as "fixed" and changing the
> status to "assigned".
> 
> I want to keep the status as "resolved" how can I change
> that assignment/process flow.

[Victor] Consider setting $g_auto_set_status_to_assigned to OFF in
config_inc.php.

The description for this configuration variable is as follows:

Automatically set status to ASSIGNED whenever a bug is assigned to a person.
This is useful for installations where assigned status is to be used when
the bug is in progress, rather than just put in a person's queue.

Regards,
Victor

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

RE: re: bug assignment flow...

Hi Victor,

Francisco's idea would work but I would need to add one
more status which i think add more complexity to the bug
workflow. I tried setting the variable to OFF works great. 

thanks
Roy.

--- Victor Boctor <victor@...> wrote:

> Hi Roy,
> 
> > When a bug/CR is assigned to a Developer and he/she
> marked
> > it as "Resolved" - The status is "resolved" and
> resolution
> > is "fixed". Which is all good and as expected. Now when
> we
> > have a new Build and the bug/CR is assigned back to QA,
> > it's keeping the resolution as "fixed" and changing the
> > status to "assigned".
> > 
> > I want to keep the status as "resolved" how can I
> change
> > that assignment/process flow.
> 
> [Victor] Consider setting $g_auto_set_status_to_assigned
> to OFF in
> config_inc.php.

RE: re: bug assignment flow... still one minor issue

Hi Victor

I spoke too soon. With that change comes a minor issue with
newly reported bug/CR. i.e when I log a new bug for a
developer the resolution is "open" which is good but the
status is "new" 
should have been assigned?

thanks
Roy

--- Victor Boctor <victor@...> wrote:

> Hi Roy,
> 
> > When a bug/CR is assigned to a Developer and he/she
> marked
> > it as "Resolved" - The status is "resolved" and
> resolution
> > is "fixed". Which is all good and as expected. Now when
> we
> > have a new Build and the bug/CR is assigned back to QA,
> > it's keeping the resolution as "fixed" and changing the
> > status to "assigned".
> > 
> > I want to keep the status as "resolved" how can I
> change
> > that assignment/process flow.
> 
> [Victor] Consider setting $g_auto_set_status_to_assigned

custom fields in View Issues page?

I've had a request to find out whether it is possible to add a custom 
field to the View Issues page. I see from the Mantis BT site that there 
is a US$ field shown there that does not appear on my personal 
installation of mantis. How does one go about doing something like 
this? Must I hack the codebase to make it work or is there a nifty 
configuration option that let's me do it more easily?

Thanks! My fellow employees like the tool, even though we're using it 
for non-bug tracking uses.

    Bo

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Re: custom fields in View Issues page?

   The "US$" field comes from enabling the sponsorship field. It  
allows people to vote with their wallet. See $g_enable_sponsorship in  
the config file.

On 8-Dec-05, at 6:36 PM, Bo Gusman wrote:

>
> I've had a request to find out whether it is possible to add a custom
> field to the View Issues page. I see from the Mantis BT site that  
> there
> is a US$ field shown there that does not appear on my personal
> installation of mantis. How does one go about doing something like
> this? Must I hack the codebase to make it work or is there a nifty
> configuration option that let's me do it more easily?
>
> Thanks! My fellow employees like the tool, even though we're using it
> for non-bug tracking uses.
>
>     Bo
>
--

-- 
Glenn Henshaw              Ottawa, Canada
Email: thraxisp4@...

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Out-of-office-reply: Mantisbt-help digest, Vol 1 #552 - 1 msg

I will be out of the office until Monday 12th December, please refer all correspondance to techsupport.england@...

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Mantis 0.19.4 Released

Mantis 1.0.0rc4 Released