Razuman i objektivan prijedlog.

A reasonable and objective proposal.

My support for this, it would be much easier to track hr.wiki related tasks. I'm surprised there's no such tag for all wm sites by default.

I'm surprised there's no such tag for all wm sites by default.

@FriedrickMILBarbarossa: Because it would be useless noise. Why should we add ~300 project tags to most tasks (when an issue happens on ALL languages), so that you will find nothing relevant anymore in project tags, plus make Phab's DB surveys slower? Please see T154549.

There is no sense in categorization for the mere sake of categorization.

Coud you elaborate on specific use cases, how you plan to use this task (your workflows), and what "directly affecting" means and what it does NOT mean?

In T291751#7382722, @Aklapper wrote:

I'm surprised there's no such tag for all wm sites by default.

@FriedrickMILBarbarossa: Because it would be useless noise. Why should we add ~300 project tags to most tasks (when an issue happens on ALL languages), so that you will find nothing relevant anymore in project tags, plus make Phab's DB surveys slower? Please see T154549.

There is no sense in categorization for the mere sake of categorization.

Is this a wrong ping? Because the quoted comment isn't mine.

Oops, indeed. I am sorry for that!

In T291751#7383098, @Aklapper wrote:

Oops, indeed. I am sorry for that!

np

In T291751#7382722, @Aklapper wrote:

Why should we add ~300 project tags to most tasks (when an issue happens on ALL languages)

No tags would mean ALL languages. One tag would mean one specific language. I do remember a few tasks that were hr.wiki-specific (Growth team features, namespace shortcuts, IAbot misbehavior, etc.), and I'm thinking it would help to have those somehow filtered so hr.wiki users can provide more input when needed. But maybe there are other ways to do that, idk.

One tag would mean one specific language. I do remember a few tasks that were hr.wiki-specific

While that makes sense to me, my impression is that the majority of Phab users do not understand that such tags are meant to be *specific* and throw them on anything that happened on a wiki (while also happening on any other wiki). See also T196740 for a similar problem we had.

Could someone answer the last question please?

Coud you elaborate on specific use cases, how you plan to use this task (your workflows), and what "directly affecting" means and what it does NOT mean?

@Aklapper Certainly, my apologies, I must've missed the question.
Phab has been seeing an increase in hrwiki-related tasks recently, mostly due to my collaboration with other tech-savy users from other wikis. As such, this tag will be very helpful in tracking tasks related to hrwiki only and perhaps implementing changes already made on hrwiki to some other projects. I am one of the only tech-savvy users on hrwiki and I assure you this will be of great help to me!

I understand and agree with your previous point - this tag is to be used only when the ticket concerns hrwiki (and possibly one or two other specific languages) but not all other languages or projects as a whole.