I was hoping to follow more or less this migration path:

1. create the new workboard in the subproject, get it reviewed by the team (name, number of columns, internal priorities)
2. and then move groups of tasks from the parent to the new workboard, while doing cleanup/triaging with the team on the way.

Part of the parent workboard is currently used by the team and the rest of SRE so it's a bit sensitive to change/iterate on anything there.

I will also flag, that subprojects will change how group membership (and watchers - iirc) effect how the parent project work, They would need to sit on the subprojects and can no longer sit on the parent project, and can't be reversed even if you disable all the subprojects (iirc).

Some teams work around this by using milestones instead of subprojects, or work around by having the "sub"projects as completing separate projects.

In T412410#11456068, @Peachey88 wrote:

I will also flag, that subprojects will change how group membership (and watchers - iirc) effect how the parent project work, They would need to sit on the subprojects and can no longer sit on the parent project, and can't be reversed even if you disable all the subprojects (iirc).

(FWIW serviceops-radar is already a subproject of serviceops, so in this case the change to how group membership works seems like it might've already happened)

Thanks for the note, as mentioned there is already another subproject so I don't expect more change with this new subproject.

Could you let me know if it can be created?

Thanks, Matthieu

@MLechvien-WMF Hi, basically see https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects
Which project name, which type, which description, etc?

If you need to regularly create projects yourself, see that link above and request permissions in T706 - thanks!

Thanks Andre for the links, I requested permissions in T706 so closing this request.