| Summary: | [RFE] add "related bugs" to bug submission template | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | libretist <sky> |
| Component: | Documentation | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED NOTABUG | ||
| Severity: | enhancement | CC: | olivier.hallot, sky, stephane.guillou |
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
|
Description
libretist
2023-12-27 22:08:05 UTC
There is an alternative bug submission form you can bookmark, which has more fields available straight away: https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice;bug_status=UNCONFIRMED;version=? The default form is simpler and focuses on the more important fields as to not be overwhelming to new contributors. Thank you! (In reply to Stéphane Guillou (stragu) from comment #1) Thank you Stéphane, but I don't see a field for "related bugs" * neither in your link * nor in the standard submission form: https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided * nor in the bug view form: https://bugs.documentfoundation.org/show_bug.cgi?id=158893 Ah, sorry, should have been clearer: the "related bugs" field you are after is called "see also". A description of the field: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/See_Also "Blocks" and "Depends on" also allow you to link to other reports, if one bug depends on the other getting fixed. (But in practice, they are mostly used for categorising with meta bugs.) (In reply to Stéphane Guillou (stragu) from comment #3) sorry, I missed it because "blocks" and "depends on" both have a form field. This is why I missed the "see also" field, although I kept looking hard for it. So maybe give it a form field so that is not overlooked (and also for the sake of consistency) ? |