Not possible to target just one series (the first task in a given context always creates a nonseries task)

I find the current behaviour as sensible default, as I want to track that the
bug is fixed in trunk as well.

Thanks,

James

I'm of a mixed mind about how to triage this -- low or wishlist. I'm glad to have the bug to track the issue, though. It has come up more than once about why you don't end up with conjoined tasks every time you target a bug to a series. I'm not sure of the reasoning for this choice historically, and I don't think we'll revisit it anytime soon, given the other higher priority work we have to do.

This could become more important to discuss again if we start improving the experience around nominating for release and targeting tasks.

Cheers,
deryck

And to clarify, since James replied, I'm not saying we will or won't change this, which is why I really didn't know how to triage it. We'll keep the bug around to track the request and revisit when it seems appropriate to do so.

On Thu, 2010-09-23 at 19:40 +0000, James Westby wrote:
> I find the current behaviour as sensible default, as I want to track that the
> bug is fixed in trunk as well.

I think the sensible default is already the default. The bug by default
is targeted at the development focus. But if one wishes to re-target the
bug to only affect a series which is not the development focus (say a
branch for the last LTS, for example), where the code has already
changed in the development focus, and therefore it does not exhibit the
bug, it is impossible to do so. There must always be a bug against the
development focus, even if it doesn't even contain code which is
affected by the bug. Instead, the only recourse is to mark it Invalid on
the development focus, which I don't think makes much sense.

If someone files a bug against a package in an LTS, and we want to link
that bug to the upstream project, we should be able to say that it
affects the series linked to the package in that LTS. If the bug then
also affects the current development focus (or perhaps any series in
between), then it can also be targeted to those series as well. But I do
firmly believe that it should be possible to target any bug to a single
series which is not the development focus.

Hmm, I was really surprised when discover current default behavior. In fact, such behavior make targeting system completely unusefull at least in projects with two or more develompment series. Moreover, projects, which change series eventually, should also has a lot of problems, because old bugs in old series, closed or not, duplicates to main project. But if developer target a bug to one of serieses, he assume that this bug concerns only this series and in most cases don't want to see it in main project.

I've try to play with targeting system in my project and simply turn my bugtracker into scrapyard because of this bug. I can't cancel targeting and can't move a bug from main project to one of series. I only can mark bug as invalid in series and in main project and when create a new one without any targeting. It's absolutely inconvenient.

So I think importance of this bug should be at least Medium, or even High.