[17:11:51] meeple27: any thoughts on how to organize the CTO backlog? in particular, how to set up projects vs tasks [17:11:59] use a column for each project? Use a parent task? [17:12:19] (I'm assuming that the primary board is for backlog/project, not for state-of-work [17:12:48] jaufrecht: I haven't thought about it at all. I don't yet have a picture in my head of how it will be used. [17:14:43] I am inclined to follow my heart, after 2 years of analyzing and reporting Phab projects [17:15:03] the only novel factor here is the Space for enforcing privacy for sensitive stuff [17:15:49] ggellerman_, have you set up any kind of audiences-wide backlog? [17:25:36] jaufrecht: I have not [17:51:31] meeple27: what are the state columns for our administrative stuff? Not Started (default), in progress, Blocked, Waiting, Done? [17:51:58] I'm thinknig Blocked and Waiting are worth separating since a lot of our stuff is, should I escalate yet, vs, this has a reasonable deadline and I'm not doing anything until then. [18:30:04] +1 to splitting those, in our case [18:49:52] is one backlog column going to be enough? Will we manually rearrange the tasks to reflect priorty? Will we use the priority field? Should we have a separate backlog board with categories, and then a kanban board?