@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
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
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
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
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
