No way to disclose (or hide) many bugs at once (without using lp APIs)

[Elliot Murphy]

It should be possible to change the visibility of multiple bugs at once.

See also bug 41702, bug 76083, bug 4153.

workarounds
===========

Write a launchpadlib script. This is particularly useful if you are (for instance) opening up a project that was embargoed.

[Björn Tillenius (bjornt)]

The work will be specced out in 1.1.8, but implemented in 1.1.9.

[Jonathan Knowles (jsk)]

Re-targeting to milestone 1.1.11 in line with re-targeting of mass-bug-editing-phase-2.

[Björn Tillenius (bjornt)]

I'm untargeting this bug since it's not a common use case. It will be fixed later if time permits.

[Elliot Murphy (statik)]

This is a common use case for project managers/developers. If I want to triage 50 new bugs and assign them out to multiple developers, mass editing would save a lot of time. Every single release I go through a list of bugs marking them fix released, and mass editing would save time there too. I've gotten specific requests for this functionality from users.

[Björn Tillenius (bjornt)]

On Thu, Jan 10, 2008 at 02:01:03PM -0000, Elliot Murphy wrote:
> This is a common use case for project managers/developers. If I want to
> triage 50 new bugs and assign them out to multiple developers, mass
> editing would save a lot of time. Every single release I go through a
> list of bugs marking them fix released, and mass editing would save time
> there too. I've gotten specific requests for this functionality from
> users.

While this is true, this bug is about changing the visibility. How often
do you change multiple bugs to be private or public?

[Elliot Murphy (statik)]

On 01/10/2008 09:39 AM, Björn Tillenius wrote:
> On Thu, Jan 10, 2008 at 02:01:03PM -0000, Elliot Murphy wrote:
>> This is a common use case for project managers/developers. If I want to
>> triage 50 new bugs and assign them out to multiple developers, mass
>> editing would save a lot of time. Every single release I go through a
>> list of bugs marking them fix released, and mass editing would save time
>> there too. I've gotten specific requests for this functionality from
>> users.
>
> While this is true, this bug is about changing the visibility. How often
> do you change multiple bugs to be private or public?
>

Sorry, didn't notice in the previous bugmail that this is about
visibility only. I withdraw my objection :)

[Brad Crittenden (bac)]

Actually there is a user who has the use case of doing mass migration of a set of bugs from private to public and they are the ones who requested this feature. We have given them the work-around to do the action via email but there does exist the use case and the scenario is like to become more important in the future.

[Matthew Paul Thomas (mpt)]

So perhaps "make public" should be available to any project driver, while "make private" is more restricted.