Maniphest T319693

Improve API Platform's Phabricator workboard(s)
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• VirginiaPoundstone
	Oct 6 2022, 6:16 PM

Description

Background/Goal

Currently, the API platform's workboard is noisy and does not allow for easy tracking of individual products and phases of work. We need to establish a Phabricator methodology and corresponding boards that achieve the following:

individual contributors can easily see all work currently assigned to them in a single view
progress on individual products is available as a single view
Product phases can be seen in separate views (Triage incoming requests, product roadmap plan, strategize, discover, define, develop, deliver, and maintenance) so we can adhere to a clean
Collaborative work across teams can be seen in a single view
product and engineering team leaders can see all API Platform work in a single view

Related Objects
Search...

Status	Assigned	Task
Open	None	T317673 <API Platform> Documentation for API Platform Value Stream Team
Resolved	• VirginiaPoundstone	T317677 Update API Platform Phab description and links
Declined	• VirginiaPoundstone	T317678 Create MediaWiki Knowledge Hub Wiki for API Platform Team
Resolved	• VirginiaPoundstone	T319693 Improve API Platform's Phabricator workboard(s)

Event Timeline

@Aklapper if you have seen other workboards, dashboards, and teams that do this well, please flag them.
Any tips greatly appreciated!

• VirginiaPoundstone moved this task from Incoming to Backlog on the API Platform board.Oct 6 2022, 6:18 PM

individual contributors can easily see all work currently assigned to them in a single view

Possible in two ways: Either change the workboard view (e.g. Group By Author or filter for Assigned To Me; see https://www.mediawiki.org/wiki/Phabricator/Project_management#Boards ), or use the non-workboard task list view on https://phabricator.wikimedia.org/maniphest/query/assigned/

progress on individual products is available as a single view

This probably means something entirely different, however I'd like to point out that I highly highly recommend not to mingle everything only into a single API Platform project tag but use additional project tags on tasks to differentiate separate codebases. See my comment T317728#8282049.

@Aklapper Thank you for pointing out the workboard and non-workboard filtering options by assignment. I will share that with the the to the team.

What you suggest for multiple tags usage is exactly what I want to move us towards. I have three follow-up questions:

is there a way to add existing project boards to the API Platform Project as a subproject without negatively affecting the existing project? For example, Thumbor Migration is now an API Platform product. Can I merge it into the API platform as a subproject?
I don't think I've come across a subproject in use example yet, do you have a link to one so I can see how it functions (as opposed to a milestone?
When should something be a subproject (limit of 16 possible as seen in the docs) and something be a milestone?

Also, I currently do not have access on the API Platform to add milestones or subprojects. Can you add that permission? Or is there someone else I need to ask for that?

@VirginiaPoundstone: I guess the question is which underlying problem you'd like to solve.... What made you think of subprojects initially? :)
See also https://www.mediawiki.org/wiki/Phabricator/Project_management#Parent_Projects,_Subprojects_and_Milestones , especially the "Here are some warnings, to avoid wrong expectations" section.

I currently do not have access on the API Platform to add milestones or subprojects. Can you add that permission? Or is there someone else I need to ask for that?

See https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects

• VirginiaPoundstone moved this task from Backlog to QA/Review on the API Platform board.Oct 25 2022, 6:59 PM

• VirginiaPoundstone moved this task from QA/Review to Should do next on the API Platform board.Oct 26 2022, 6:48 PM