[Pywikipedia-bugs] [Maniphest] [Commented On] T194009: Herald rule for adding Upstream when a task is moved to "Upstream issues" column of pywikibot-core workboard

MarcoAurelio added a comment. This can now be done using the Triggers functionality, but you'll need to agree on which tag you'd like Phabricator to be adding to the tasks in said column. From what I'm reading, it looks #upstream might be

[Pywikipedia-bugs] [Maniphest] [Commented On] T194009: Herald rule for adding Upstream when a task is moved to "Upstream issues" column of pywikibot-core workboard

Dvorapa added a comment. Sure, that's why I was removing #upstream this from Pywikibot-MW API tasks if it was an API issue yesterday TASK DETAIL https://phabricator.wikimedia.org/T194009 EMAIL PREFERENCES

[Pywikipedia-bugs] [Maniphest] [Commented On] T194009: Herald rule for adding Upstream when a task is moved to "Upstream issues" column of pywikibot-core workboard

Aklapper added a comment. In my interpretation of https://phabricator.wikimedia.org/project/profile/153/ , #upstream is "external". See https://www.mediawiki.org/wiki/Upstream_projects TASK DETAIL https://phabricator.wikimedia.org/T194009

[Pywikipedia-bugs] [Maniphest] [Commented On] T194009: Herald rule for adding Upstream when a task is moved to "Upstream issues" column of pywikibot-core workboard

Dalba added a comment. In T194009#5188159 , @Dvorapa wrote: > I don't like marking tasks as #upstream . > > For example if the task is #mediawiki-api

[Pywikipedia-bugs] [Maniphest] [Commented On] T194009: Herald rule for adding Upstream when a task is moved to "Upstream issues" column of pywikibot-core workboard

Dvorapa added a comment. I don't like marking tasks as #upstream . For example if the task is #mediawiki-api bug and is marked with #mediawiki-api

[Pywikipedia-bugs] [Maniphest] [Commented On] T194009: Herald rule for adding Upstream when a task is moved to "Upstream issues" column of pywikibot-core workboard

MBinder_WMF added a comment. FWIW, this can be worked around if the column is a Milestone, as Milestones are technically projects, and thus have tags that Herald can detect. The challenge is that this is using Milestones in a way they aren't really meant to be, so there are other restrictions that