Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Restricting bugzilla issues creation/edition?

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 <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@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



Back to the top