- User Since
- Mar 27 2015, 5:03 PM (241 w, 3 d)
Mar 7 2017
@20after4 : Ah. So by default, everyone just gets a "create task" option, which would never use any custom forms or subtypes. That does seem to resolve my concerns (although I still think it would be cool for phab to behave differently depending on which project(s) I was viewing).
Mar 6 2017
Our phabricator instance (WMF) is shared by many(!) different projects and teams. If I understand the current proposal, all the subtypes and forms would be available to all users across all teams and projects, except where specific access is limited (e.g. security issues). I think that forces us to either: a) have very few subtypes, which manage to achieve consensus, or b) have a lot of subtypes, which would mean that everyone's "create new" menu would be very cluttered.
Sep 19 2016
@lyahdav : That looks pretty cool. It's not quite clear to me where it runs. Is this a script that one would install on the same box that phab itself is running on?
Aug 2 2016
I have no idea what percentage of phabricator current or future users will be task-count-centric rather than story-point-centric. Speaking generally, the Kanban ideal would use task counts, not points. (As compared to the Scrum and XP ideals, which would use points.)
The specific request of the WMF teams is for the workboard column WIP limit to be measured in task count rather than story points. We have been directed to this task for that request, although it's not clear to me that they are actually the same thing. We really don't want to treat tasks as if they had a story point value of 1.