Re: [cross-project-issues-dev] Restricting bugzilla issues creation/edition?

[Mickael Istria]

@Denis and Infra team: can such restrictions be setup on Eclipse Bugzilla
instance? If so, I guess it's only a matter of opening a bug when project
is ready to migrate, isn't it?

On Fri, Mar 19, 2021 at 9:42 AM Mickael Istria  wrote:

> [...]
> One approach would be to make the BZ tracker progressively "read-only", or
> at least to prevent from creating new issues.
> For a given product, is it possible to prevent creation of new issues? Is
> it possible to block creation of issues while keeping edition access on
> existing issues? Is it possible to make the product issues "read-only" (no
> creation, no edition)? All that without removing the product backlog.
> My favorite one at the moment would be to block creation of new issues but
> still allow edition.
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Restricting bugzilla issues creation/edition?

[Mickael Istria]

On Fri, Mar 19, 2021 at 10:28 AM Rolf Theunissen 
wrote:

> RTFM:
> https://bugzilla.readthedocs.io/en/5.0/administering/categorization.html#basic-product-group-restriction
> Based on group permissions it is controlled who can enter, edit, read,
> etc., on a product granularity,  So it should be possible to disable
> create, while remain edit rights.
> (Sorry to be blund, but manuals do have value although engineers tend to
> just ignore them)
>

OK, so it's technically possible for Bugzilla in general. As I'm not a
Bugzilla admin, I'm more curious about whether it's something EMO
Infrastructure team can set up on bugs.eclipse.org.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Restricting bugzilla issues creation/edition?

[Rolf Theunissen]

RTFM:
https://bugzilla.readthedocs.io/en/5.0/administering/categorization.html#basic-product-group-restriction
Based on group permissions it is controlled who can enter, edit, read,
etc., on a product granularity,  So it should be possible to disable
create, while remain edit rights.

(Sorry to be blund, but manuals do have value although engineers tend to
just ignore them)

Op vr 19 mrt. 2021 om 09:43 schreef Mickael Istria :

> Hi all,
>
> I'm brainstorming about how to have a complete the migration to GitHub for
> some projects (eg m2e, Tycho...). Currently, the main pain point would be
> the bug tracker: the backlog on Bugzilla is huge and migrating it to GitHub
> wouldn't be very relevant, but this backlog needs to remain accessible.
> One approach would be to make the BZ tracker progressively "read-only", or
> at least to prevent from creating new issues.
> For a given product, is it possible to prevent creation of new issues? Is
> it possible to block creation of issues while keeping edition access on
> existing issues? Is it possible to make the product issues "read-only" (no
> creation, no edition)?
> My favorite one at the moment would be to block creation of new issues but
> still allow edition.
>
> Thanks in advance for your insights.
>
> --
> Mickael Istria
> Eclipse IDE 
> developer, for Red Hat Developers 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Restricting bugzilla issues creation/edition?

[Christoph Läubrich]

I don't know if it is possible in Buzilla but Github support "issue 
templates" (that is some predefined text is filled when creating a new bug).


If that also possible with Bugzilla one could simply put the info that 
Github should be used as the default text if someone tries to open a new 
report including a link to Github issues.


Am 19.03.21 um 09:42 schrieb Mickael Istria:

Hi all,

I'm brainstorming about how to have a complete the migration to GitHub 
for some projects (eg m2e, Tycho...). Currently, the main pain point 
would be the bug tracker: the backlog on Bugzilla is huge and migrating 
it to GitHub wouldn't be very relevant, but this backlog needs to remain 
accessible.
One approach would be to make the BZ tracker progressively "read-only", 
or at least to prevent from creating new issues.
For a given product, is it possible to prevent creation of new issues? 
Is it possible to block creation of issues while keeping edition access 
on existing issues? Is it possible to make the product issues 
"read-only" (no creation, no edition)?
My favorite one at the moment would be to block creation of new issues 
but still allow edition.


Thanks in advance for your insights.

--
Mickael Istria
Eclipse IDE  
developer, for Red Hat Developers 


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev


___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Restricting bugzilla issues creation/edition?

[Mickael Istria]

Hi all,

I'm brainstorming about how to have a complete the migration to GitHub for
some projects (eg m2e, Tycho...). Currently, the main pain point would be
the bug tracker: the backlog on Bugzilla is huge and migrating it to GitHub
wouldn't be very relevant, but this backlog needs to remain accessible.
One approach would be to make the BZ tracker progressively "read-only", or
at least to prevent from creating new issues.
For a given product, is it possible to prevent creation of new issues? Is
it possible to block creation of issues while keeping edition access on
existing issues? Is it possible to make the product issues "read-only" (no
creation, no edition)?
My favorite one at the moment would be to block creation of new issues but
still allow edition.

Thanks in advance for your insights.

-- 
Mickael Istria
Eclipse IDE 
developer, for Red Hat Developers 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev