[18:47:47] ggellerman_: meeple27_ maxbinder awjr jaufrecht nataliaharateh I unfortunately have a meeting conflict with staff meeting - I did do a little agenda cleanup in the meeting doc. I don't think there's anything on there that I am critical for. Apologies fro missing. [18:48:26] kristenlans: np! I can facilitate if that would be helpful [18:54:07] no worries kristenlans 👍👍 [18:59:27] ggellerman_: that woudl be rad :-) [18:59:41] kristenlans: will do [19:59:36] nataliaharateh: Do you plan to do the "How TPG uses LE surveys" survey? Or you think you don't have a long enough baseline? [19:59:56] not saying you are the only person left but you are the only person left now that I finally just did it. [20:07:14] I think I don't have a long enough baseline jaufrecht [20:07:27] sorry for blocking! [22:13:31] maxbinder et al: Is there a way to have a Phabricator board in which you can drag a task from Column A to Column B without the task losing its association with Column A? Willing to accept project/sub/project/milestone whatever in place of "Column A", so long as drag and drop on a board is still possible. [22:24:48] jaufrecht: according to phab docs, a task cannot exist in more than one column at a time [22:36:29] this is how I feel about that: https://www.youtube.com/watch?v=ybGOT4d2Hs8 [22:36:36] (sfw, I think) [23:16:04] jaufrecht: What's your use case? It makes sense to me that you can't have a task in more than one column on a single board. [23:19:02] https://phabricator.wikimedia.org/project/view/1613/. should be same pattern as TPG: I want to have a board where each column is a different category (aka Epic aka tranche aka project (not Phab project, just project), and I want to have a column for "Do this now" [23:19:15] and I want to drag stuff from the projects to the "do this now" column without losing track of which project they came from [23:19:46] could do it with Phab + Phlogiston by making them all subtasks of a "Category"-tagged epic, but that's a moderate amount of overhead [23:31:30] coincidentally, I ran into a similar use case today, where that would be handy. But the limitation seems reasonable to me, so I'm not feeling thrash metal about it [23:35:28] related: it seems redundant for tasks to be tagged with both "TPG-Epics (Establish Metrics for Light Engagements)" and "TPG-FY2016-17-Q2-LE-Metrics". Is there a way to consolidate that? [23:37:00] 06Team-Practices, 10TPG-FY2016-17-Q2-LE-Metrics, 10TPG-Epics (Establish metrics for Light Engagements), 15User-JAufrecht: Enumerate any external-to-TPG uses for LE Survey data - https://phabricator.wikimedia.org/T152469#2849341 (10JAufrecht) [23:38:35] 06Team-Practices, 10TPG-FY2016-17-Q2-LE-Metrics, 10TPG-Epics (Establish metrics for Light Engagements), 15User-JAufrecht: Validate any external-to-TPG uses for LE Survey data - https://phabricator.wikimedia.org/T152469#2849341 (10JAufrecht) [23:41:05] 06Team-Practices, 10TPG-FY2016-17-Q2-LE-Metrics, 10TPG-Epics (Establish metrics for Light Engagements), 15User-JAufrecht: Sync LE Survey uses with other TPG-related Survey uses - https://phabricator.wikimedia.org/T152470#2849363 (10JAufrecht) [23:41:58] 06Team-Practices, 10TPG-FY2016-17-Q2-LE-Metrics, 07Epic, 10TPG-Epics (Establish metrics for Light Engagements), 15User-JAufrecht: [EPIC] Establish metrics for Light Engagements - https://phabricator.wikimedia.org/T147354#2690235 (10JAufrecht) [23:59:49] jaufrecht: my understanding was that after the experiment, one of those 2 would disappear