<3. Thanks!

• Create a new tag, for example "translatewiki-support-requests". This will make continuous triaging easier. I'm currently (slowly) triaging the huge i18n board, and there are many tasks of this kind there.

Whatever is helpful. I've added you to #acl*Project-Admins so you could create this following the naming/icon/color guidelines.

• Add some boilerplate text that will suggest good message bug reporting practices.

We link to https://mediawiki.org/wiki/How_to_report_a_bug at the top by default (not sure if that's displayed though, never tried to report by clicking from twn).

• Remove ----. It creates unnecessary Phabricator formatting.

Either remove, or simply add empty lines before and after.

• Add the relevant tag automatically. Currently it adds "MediaWIki-General-or-Unknown" and "i18n". Perhaps a tag could be configured in translatewiki group configuration for each project.

If it's not possible to add the relevant tag automatically I'd appreciate removing "MediaWiki-General" and "I18n" in general. IMO small typos are simply not an I18n issue.

I support these ideas. Would be nice if someone picked this up, I can provide guidance.

What would a multiplication of tags help?

What "multiplication"? Discussion here mentions creating 1 additional tag, based on the task source (translators), to allow finding/triaging those incoming tasks, as those tasks are not always I18n tasks by definition.

In T188379#4009485, @Aklapper wrote:

What "multiplication"? Discussion here mentions creating 1 additional tag, based on the task source (translators), to allow finding/triaging those incoming tasks, as those tasks are not always I18n tasks by definition.

Indeed. The i18n tag didn't get the attention it deserves for a long time, and accumulated more than a 1000 unsorted tasks. I am slowly triaging them now. Having a separate thing for translatewiki will make it more convenient.

The i18n tag didn't get the attention it deserves for a long time

And this despite being one of the most watched and followed tags we have. How can a less visible tag help anything?

This is not about technical solutions but about workforce. For over 5 years I triaged approximately all i18n and twn reports, then I couldn't continue at the same pace. The solution is to divide the labor more equally, and the I18n tag works reasonably well in that regard, although of course it cannot make new people appear from thin air.

Because it would prevent these issues from going into a bucket of unrelated and unsorted tasks.

Where to find that link to Phab's task creation form in some code repository file which is deployed on translatewiki.net?

https://github.com/wikimedia/translatewiki/blob/master/TranslateSettings.php#L29-L32 (use Gerrit for patches)

Change 432430 had a related patch set uploaded (by Aklapper; owner: Aklapper):
[translatewiki@master] Phab reporting: Fix format; remove mostly wrong generic MW project tag

https://gerrit.wikimedia.org/r/432430

Change 432430 merged by jenkins-bot:
[translatewiki@master] Phab reporting: Fix format; remove mostly wrong generic MW project tag

https://gerrit.wikimedia.org/r/432430

In T188379#4202334, @gerritbot wrote:

https://gerrit.wikimedia.org/r/432430

This tagging is contrary to Phabricator usage guidelines, which require a component.

I'm also worried that "translation issue" may be misread as meaning "the translator did something wrong" (such reports don't belong here) or "it's not a code/developer issue".

In T188379#4202335, @Nemo_bis wrote:

This tagging is contrary to Phabricator usage guidelines, which require a component.

Reporters are more than welcome to follow usage guidelines by setting a component, instead of having software setting a (nearly always) wrong component.

I'm also worried that "translation issue" may be misread as meaning "the translator did something wrong" (such reports don't belong here) or "it's not a code/developer issue".

"i18n issue" could also be (and has sometimes been) misunderstood as "the translator did something wrong", hence not a new problem, now there is just a less cryptic and slightly more correct default task summary.

Maybe a new column in translatewiki.net called "Support requests"? Or a milestone for said project called "support requests"?

The translators are not likely to know which component to use. It would be good to have a separate tag so that a human can go through and help to connect the dots. I would not use #translatewiki because the issues are not with translatewiki.net.

If someone feels energetic they can also provide a list of matching tags for each extension when available so that we can improve our automatic tagging.

It would be good to have a separate tag so that a human can go through and help to connect the dots.

It would be ok to have a separate tag #MediaWIki-Unsorted or similar, or at least an umbrella tag for all MediaWiki (core) components (cf. T76942), but that's up for the MediaWiki developers to decide. For now, MediaWiki-General is the only possible component.

If someone feels energetic they can also provide a list of matching tags for each extension when available so that we can improve our automatic tagging.

Indeed this was the ultimate goal, but we started configuring the link depending on the namespace rather than the message group.

Change 439998 had a related patch set uploaded (by Nikerabbit; owner: Federico Leva):
[translatewiki@master] Restore more accurate MediaWiki reporting parameters

https://gerrit.wikimedia.org/r/439998

Change 439998 abandoned by Nikerabbit:
[translatewiki@master] Restore more accurate MediaWiki reporting parameters

Reason:
Stuck. Hopefully will be superseded by project specific configuration.

https://gerrit.wikimedia.org/r/439998

There is more flexibility now, but I am curious which of the issues still persist from the POV of a bug triager?

Allow to define a code repository URL so people don't file tickets here when the corresponding piece of software does not use Wikimedia Phabricator.

To my knowledge we are redirecting most project support request to the correct place now.