Req #81271 [Opn->Nab]: Issue tracker: Allow categorizing reports about bugs.php.net ITS

Edit report at https://bugs.php.net/bug.php?id=81271&edit=1 ID: 81271 Updated by: danack@php.net Reported by: chealer at gmail dot com Summary: Issue tracker: Allow categorizing reports about bugs.php.net ITS -Status: Open +Status: Not a bug Type: Feature/Change Request Package: Website problem PHP Version: Irrelevant Block user comment: N Private report: N New Comment: Reporting issues about how you find the tracker difficult to use, when you haven't made any contributions is not helping. It takes up time from people triaging the bugs, and figuring out if they need to be urgently looked at. Please can you stop opening issues like these until you've made a code contribution. If you're looking for stuff to work on, the docs at https://github.com/php/doc-en and https://github.com/php/doc-fr are there for PRs. Previous Comments: ------------------------------------------------------------------------ [2021-07-18 15:09:26] chealer at gmail dot com Description: ------------ This tracker categorizes tickets about meta-issues affecting this very issue tracking system in the "PHP.net Website problem" package. There are many issues with the ITS, but even more other php.net problems, so identifying the ITS-specific issues is time-consuming. Several reporters tried to use conventions about ticket titles to distinguish tickets about bugs.php.net, but some are undesirable, and there are too many: Starting with "[bugsnet]": https://bugs.php.net/bug.php?id=78962 Starting with "[bugs.php.net]": https://bugs.php.net/bug.php?id=67657 Starting with "[Bug tracker]": https://bugs.php.net/bug.php?id=70411 Starting with "[BugTracker]": https://bugs.php.net/bug.php?id=70411 Starting with "Issue tracker:": https://bugs.php.net/bug.php?id=77354 Starting with "ITS:": https://bugs.php.net/bug.php?id=77356 My own preference is for "Issue tracker", but even I had to use "ITS", because my title wouldn't fit in the limited number of characters allowed had I used the former. Adding a unique way to specifically categorize ITS tickets would uniformize and greatly diminish the risk of duplicate reports. Test script: --------------- This does not report a bug. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=81271&edit=1