Hi,
I'm no longer a Miraheze Sysadmin.
Can User-RhinosF1 be updated to replace the Miraheze-Linked column with a project? Please also update the linked herald rule.
The new project should be for:
Thanks!
We tend to not have projects for our downstream end users from my understanding, is one for Miraheze really needed? and will it's currently sysadmins watch and monitor it?
tasks reported because it was found on a Miraheze wiki
Is there a need to task these tasks? Shouldn't these already be tracked in some fashion on the downstream task system? (I know we have them for several of the WMF projects, but i'm not sure if they really bring any net value to task tracking on our installation)
tasks needing downstream Miraheze support
Shouldn't these just get closed and have the task creator directed to the down stream task system? Having multiple tasks around just causes comment fragmentation
Yes, it will be monitored.
tasks reported because it was found on a Miraheze wiki
Is there a need to task these tasks? Shouldn't these already be tracked in some fashion on the downstream task system? (I know we have them for several of the WMF projects, but i'm not sure if they really bring any net value to task tracking on our installation)
Not every user manages to report to the right place. We have a herald rule that attempts to catch all tasks where Miraheze is mentioned to notify us via my project currently. We also close tasks once upstreamed. This avoids multiple users being subscribed.
tasks needing downstream Miraheze support
Shouldn't these just get closed and have the task creator directed to the down stream task system? Having multiple tasks around just causes comment fragmentation
Not every task needing downstream support needs closing. What if it's just waiting on an exception trace? Or for feedback about proposed code changes affecting an extension?
We have some #affects-someOtherProjectOrWebsite style project tags in Wikimedia Phabricator, if that's being asked for. See e.g. https://phabricator.wikimedia.org/project/profile/4381/
However, tasks with such project tags should also always have another project tag which "explains" which Wikimedia upstream codebase the ticket is about.
Is that what's being asked for here?
Herald rule seems to be H342 from T240987?
Yes. A task should never only have the Miraheze tag on. It should also have another tag for whichever codebase/feature /RfC it is about/refers to.
Herald rule seems to be H342 from T240987?
Yes. That's the one. The description part will need to be updated to use the new tag (and no need really to add me as a subscriber because the project tag does that anyway. Just add my user project only when I'm assigned.)
Requested public project tag affects-Miraheze has been created: https://phabricator.wikimedia.org/project/view/6096/
(In case you need to edit the project or project workboard itself at some point and lack permissions, please see Trusted-Contributors.)
Interested people are welcome to join the project as members, and to watch the project in order to receive notifications on task updates.
Recommended practices for project and workboard management in Phabricator are available.
I changed Herald rule H342 to be only about "Add User-RhinosF1 project tag when task is assigned to RhinosF1".
Is there also a need to have a rule which is about "When description contains miraheze, then first time add project affects-Miraheze" or sth like that?
Created H406 called Add #affects-miraheze [T315160; T240987]:
If Description contains: miraheze, Then first time: Add projects: affects-Miraheze