Phabricator UpdatesPublicAnnouncements, Updates and discussion of new features in Wikimedia's Phabricator | General support: mw:Talk:Phabricator/Help
Thanks @Aklapper , I chimed in.
Tangentially: One team would like to categorize their tech debt. Up to now, they have been using Technical-Debt but, since that is a global tag, they can't use columns to track what type of tech debt it is for them. As a result, they created a team-specific tech debt tag, which seems somewhat redundant. It also seems to be the only way they can track their categories of tech debt without adding disruptive columns to their backlog. Is there a better way to approach this? Milestones or Subprojects of Technical-Debt maybe (I'm just throwing ideas out there)?
So Technical-Debt would have a milestone called "Team X"? Benefits: They can have as many of their own columns as they want in "Technical-Debt (Team X)". And "Technical-Debt" and "Technical-Debt (Team X)" will have a clear relationship as parent->milestone, so that a) it's clear they are related and not duplicates, and b) searches for Technical-Debt will return these as well. Con: the new milestone will appear as "Technical-Debt (Team X)" in some contexts, and Team X in others; could be hard to find in search?
Defined at https://www.mediawiki.org/wiki/Team_Practices_Group/Glossary#Story_points. Some notes on how it's used by WMF teams can be found in https://www.mediawiki.org/wiki/Phabricator/Project_management (you'll need to search for "story points" in the body). It could probably be made clearer; if you have ideas on how to do that, like what questions need to be answered, please be bold in updating the documentation or asking more questions.
@Aklapper @mmodell After reflection, I agree with Andre's assessment that #bug is too risky because submissions will occur only with #bug and no actual code project. Barring a Herald that adds a project that tracks orphan tasks (#unknown or something), and someone attending to those, I think individual team bug tracking is simpler (e.g. iOS-app-Bugs , Android-app-Bugs ) despite the risk of redundant projects.
Does disabled accounts continue to receive mails and updates? Would be any issue if I remove them from a task? I ask because @LuisV_WMF is disabled but on email updates I get from tasks where he was subscribed (cf. T5233), it continues to appear in the email footer as CC, like if an email were also sent to them. Thanks.
Hi again. Is it possible or will it be to move a task from several workboards categories at once from the task menu itself, instead of having to do this one by one? Also, it'd be interesting that tasks could automove to different categories based on the status or tags of the task. For example: if the task is marked at resolved, the task moves itself to the "Closed" column of the workboard, based on per-workboard configuration. Thank you.
(meta: I feel that support questions should go to https://www.mediawiki.org/wiki/Talk:Phabricator/Help but I have no idea what this Conpherence chat room is about either "Interested Parties - Discussion about Phab" so this might be on-topic.)
Just a heads up for those who are interested. Team practices and product managers might be interested in this especially: Upstream just merged a fairly major change: https://secure.phabricator.com/T12314 which will make it possible to resolve T92708: Add fields to support bug specific information but there is some configuration involved and we'd need to think about how to best take advantage of it.
I intend to move forward with T92708: Add fields to support bug specific information in the coming weeks. Any further input would be welcome before I create a bunch of new task fields for the "Bug" task type.
That's something to discuss in https://phabricator.wikimedia.org/rPHEX8d9e072ddf25d0f3aebdfc9bc270b779a21a5b08#2294458 as it's not related to any new features or updates of the Phabricator codebase, I'd say.
Task Close Date:
Maniphest now explicitly tracks a closed date (and closing actor) for tasks. This data will be built retroactively by a migration during the upgrade. This will take > a little while if you have a lot of tasks (see "Migrations" below).
The Maniphest search UI can now order by close date and filter tasks closed between particular dates or closed by certain users. The maniphest.search API has similar support, and returns this data in result sets. This data is also now available via Export Data.
For closed tasks, the main task list view now shows a checkmark icon and the close date. For open tasks, the view retains the old behavior (no icon, modified date).
@mmodell: Indeed. I added a comment to https://www.mediawiki.org/wiki/Topic:Tztjlvbtpojf3bpq about it. I also created https://phabricator.wikimedia.org/project/view/3241/ for other issues that got reported in Wikimedia.
@mmodell That new feature for filtering on close date/range is great, thanks for the update. I'm finding that if I manipulate closed tasks, it still sends notifications to subscribers to those tasks. This is likely by design, but when one needs to sort out, say, a whole quarter's worth of closed tasks, it's a lot of notifications that are not necessary. My understanding is that we have a special WMF-Phab account for batch changes that can circumvent notifications, so as not to spam people and IRC bots. Would that account also be able to handle manual changes to a board? That is, could I login to it and move the tasks around? I'd much rather do it by batch, but the only equivalent feature is "Move Tasks to Column..." and that seems to only affect tasks with Status=Open, so I have to do that manually. I don't mind, but it does make me wonder if that special account can handle this use-case. :)
There's the account https://phabricator.wikimedia.org/p/Phabricator_maintenance/ . Regarding use cases, it's just an account that creates no notifications. I don't see why "Move Tasks to Column..." should only affect open tasks.
Sorry, hit enter! And then my connection to Phab died, so apologies if this message is repeated. Regarding "Move Tasks to Column..." I agree. I expected it to behave the same way as "Bulk Edit Tasks..." or the old "Batch Edit Visible Tasks..." (I think that's what it was titled), but alas. Anyway, we can probably discuss that in another place. :)