[16:57:16] nataliaharateh: PDU: https://www.allacronyms.com/PDU/Pokemon_Digimon_United [16:58:08] (or more seriously, I assume Professional Development Unit), a PMI (Project Management Institute) thing [16:58:38] excellent question, btw. I had no idea, but just ignored it in the spreadsheet [16:58:51] thanks meeple27 :D [17:44:33] is anyone aware of any significant issues with Phab sub-projects? Is it safe to convert an existing project to a sub-project given the "Subprojects and milestones are only partially implemented" warning on Phab? [17:47:45] ^ jaufrecht maxbinder [17:48:41] sub-projects aren't broken. It's more that the conceptual model is only half-implemented. What this means is that you get fairly arbitrary limitations. [17:49:25] nataliaharateh: I wouldn't recommend it. It's a partially deployed feature, and the feature itself provides minimal benefit with added restriction. [17:49:25] A great example is in the report Max and I made for the TPG board arrangement, where we show how making TPG-Engagements either a milestone or a sub-project would help or hurt a bunch of specific workflows. [17:49:38] If it was fully implemented, none of those trade-offs would exist. [17:50:01] What Joel said [17:50:21] thanks Max & Joel, will look at that doc! [17:50:43] the main benefit currently implemented is probably that when you search for a project, you also match on the sub-project tasks. what problem are you trying to solve? [20:59:04] Looking through the board proposal and can't seem to find the sub-project option - scenario 1 - Engagements Milestone is a separate board turned into a milestone, scenario 2 - Epgagements - engagements are milestones on the epics board, scenario 3 - Engagements Board - new board filled with engagements as milestones. Which one is the sub-project scenario? Am [20:59:05] I looking at a wrong doc (https://docs.google.com/document/d/1G7FkrIfqhhmqSxaRLf3RcJlgSGb7zlpBco58iqzO-II/edit#heading=h.t46r8p1akp1y)? 🤔