We're going to limited to what they are and what they do, as long as their buried inside Projects. We should just make it a full application. The main idea here is I want an easy way to 'dock' different projects like tabs and just be able to move between them while still in board-mode.
I'd like to flesh this out a bit more before committing to it, but I'm generally open to it. Two things that came up somewhere:
- workboard of a user's tasks (vs a project's tasks)
- workboard of projects (vs tasks)
Not really convinced either of these are like super great ideas, but they're off the table with boards inside projects.
On the other hand, workboards probably have a better chance of interacting sensibly with subprojects if they remain closely tied to projects, but that's not very well fleshed out either.
My rough though (before I get Balsamiq out) is that we have both the sub-projects task and the swamp of suck homepage task ahead of making workboards more accessible/workable for various people. I think if we approached it more on a meta-container level, we could build something that would meet all needs before those other tasks.
By default "Workboards" is an app which shows you a tabbed interface at the top with projects you are a member of. You can reorder the tabs, and the first tab is the Workboard default. Each tab below show's that projects workboard.
People can make other "Workspaces" in Workboards which are sets of Projects. This allows managerial types to have groupings of projects they may want to watch, but don't belong to. You might have an "F8" Workspace that tracks all the Projects launching at your companies F8 conference. Another example is Sprints. You could have "Maniphest" be your Workspace and "Maniphest.S1", "Maniphest.S2", "Maniphest.S3" as your Projects.
Additional Board Types like "Personal", where I can move my tasks to how they relate to me personally. As in, stuff Im working on now, upcoming, backlog.
@chad - on your alpha, how do you think about the "choose which project / workboard" UI when the user is a member of N projects where N is fairly large? Evan probably has the right N to stress test it on this instance today.
I like the alpha -> beta. I'd probably just call "workspaces" "workboards" though, and potentially for v1 allow ways to define them beyond even just projects. (e.g. values of custom fields on the tasks.)
What if Chad's thoughts on https://secure.phabricator.com/T4890#6 were instead implemented as a default view on Maniphest? (i.e. application search is something you have to click through to, and otherwise its this more boards-based view?) We can put some of the existing default application search items as automagic workboards (as in Chad's mock) / make it easy to make workboards that show those search results in workboard form.
I guess the question to me is maybe the existing "list of tasks" UI is not particularly useful / a 1 column board, and its better to just always be looking at a board?
I like the workspace bit a bunch, particular if it lets us get away with "workspaces" and "projects" (and not need subprojects. I think we might need to work on custom fields a tad more usability / discoverability wise to iron out the other subproject needs.) Someting like T4893 may be solvable here too.
If we plan on keeping workspace + maniphest as fairly distinct, I think its important we don't pollute the project namespace for either use case. For example, if it makes sense to be adding projects like "Maniphest.Sprint5" in workboards, I'd want those projects to feel correct while using maniphest. Not sure if it would be a problem as layed out; just a consideration I want to keep in mind.
@btrahan, I'd solve it both in the UI (with tabs that collapse at the end into a dropdown) and with "Workboards" (Project Buckets inside the Workboard app). I'm leaning towards just a full-fledged product management app that ties into every other application rather than stay buried in Projects. I think it's both more intuitive to have a separate space, and something that will allow more flexibility. I have minor concerns Projects in general are getting overloaded and this would keep them separate.
(I haven't thought about this carefully, but another possible attack here is making a "dock" widget and a "board" widget and driving this through dashboards, although that might create a bunch of other problems.)
I think the benefits to a solo application outweigh the downsides. Actually, I'm not sure there is any downside since I think eng/design costs are lighter.
- With a full app, we can truly focus on "Product Management" in one place
- We don't need to make compromises in other apps to support all community feedback
For example, making it the default in Maniphest both disrupts how the community currently works there and loosely ties Workboards directly to Task Objects only (or mostly). T2628 comes to mind specifically. I can see wanting other Object Types on Workboards. I think Atlassian allows diffs to be on their boards. Why not have Workboards for Pholio? It might happen.
Adding to homepage (shortcuts to boards) should happen anyways, I don't think this would impact that. I think design/eng time on a homepage is probably pretty great if we want to do it well. At least on my end.
Adding to Projects or making it a default view of Projects is possible, but if we called Projects the more aptly named "Tags", I don't know that we would do that. This is my concern on limiting applications, Projects should be about managing the containers, not building weekly Sprints.
Uninstallable. Don't want it? Cool, uninstalled.
I think I may be able to rough my concept out with a little stretch of time, at least I'd rather discuss this over a working Alpha design to see what the feedback would be like. I think just an app, and a sidebar of your projects is all that's needed to feel this out.
I'm more used to work with Atallassian Jira and GreenHopper (now Agile).
What I think would be just great would be to have something like that in Phabricator.
Just my 2¢ :)
I have seen you mentioning this Personal workboard in a couple of places. Has this idea a task on its own? I couldn't find it. It's a very good idea.
Right after announcing Wikimedia Phabricator registration open for everyone, we got already this request from one of our developers: https://phabricator.wikimedia.org/T555