When targetting a bug, properties should be inherited from "parent" bug

[Fernando Perez]

When an existing bug for a project is 'targeted' (via the 'target to' button) to a release series, it seems logical to at least inherit the properties of the parent bug (status, assigned to, importance, etc). Right now if you are rapidly triaging bugs in a project and targetting them to a series, you need to manually re-write all those fields for each bug.

[Ursula Junque (ursinha)]

Hi Fernando,

I'm not sure I understood well the issue. When you target a bug to a release, you're just saying the bug should be fixed in time for that release, so every bug is a separated one.
What you're suggesting is that you want to be able to do bulk changes to bugs, like, select a bunch of them and target all to a milestone, change the status and so on. If so, there's already a bug reported for that. Could you confirm if is that the case, please?

Thanks!

Ursula

[Fernando Perez (fdo.perez)]

Hi Ursula,

On Fri, Jul 31, 2009 at 12:17 PM, Ursula
Junque<email address hidden> wrote:
> Hi Fernando,
>
> I'm not sure I understood well the issue. When you target a bug to a release, you're just saying the bug should be fixed in time for that release, so every bug is a separated one.
> What you're suggesting is that you want to be able to do bulk changes to bugs, like, select a bunch of them and target all to a milestone, change the status and so on. If so, there's already a bug reported for that. Could you confirm if is that the case, please?

Sorry if I didn't make myself clear enough. Let's say for example
that I have this bug:

https://bugs.launchpad.net/ipython/+bug/366209

and I decide that I should really fix it before the upcoming ipython
0.10 release. So in the bug page, I can click on "Target to release",
next to the little clock-looking icon, and it will open the 'nominate'
page where I can choose the 0.10 series. But when I do that, the box
with "affects, status, ..." etc gets a new line, though it's still the
same bug.

What I'm suggesting is that this new series-specific sub-entry at
least should inherit the properties of the starting bug, since it is
the same bug. Right now, that starts as if it were a new bug, without
any of the fields being filled.

I hope that's clearer, I'll be happy to discuss it further to clarify things.

Thanks!

f