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 <mist...@redhat.com>: > 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 <https://www.eclipse.org/downloads/eclipse-packages/> > developer, for Red Hat Developers <https://developers.redhat.com/> > _______________________________________________ > 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
