Page MenuHomePhabricator

Create team-practices-this-week project
Closed, ResolvedPublic

Description

The TPG would like to create a new project in which to track it's weekly work, and to re-purpose its existing project for the purpose of triaging, maintaining a general backlog of tasks, and tracking non-actionable tasks.

Project request details:
Name: Team-Practices-This-Week
Description: The weekly workboard for the Team Practices Group. This is where the Team Practices Group tracks work it has committed to each week.
Type of project: Sprint

Event Timeline

Awjrichards raised the priority of this task from to Needs Triage.
Awjrichards updated the task description. (Show Details)
Awjrichards added a project: Project-Admins.
Awjrichards moved this task to Incoming on the Project-Admins board.
Awjrichards added a subscriber: Awjrichards.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 2 2015, 10:33 PM
Awjrichards closed this task as Resolved.Mar 4 2015, 1:21 AM
Awjrichards set Security to None.

@Awjrichards: Please always set a start and an end date for sprints. If not set, https://phabricator.wikimedia.org/project/sprint/ just displays an error instead of the list of sprints. Also, please use green color for sprints, as explained on https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects (fixed now).

Note that Phab admins could set up a Herald rule to automatically add the Team-Practices project whenever Team-Practices (This-Week) is added. If that is wanted.

Thanks @Aklapper, I missed the color requirements in the docs (should have read more closely).

Is it currently convention to have tasks in a parent project as well as in a specific sprint? I'm not necessarily opposed to the idea, but it seems like it adds more overhead for managing tasks (moving it into an additional column on one board and editing it to add an additional project). The workflow now is that we keep a general backlog in Team-Practices and then when we're ready to commit to working on something for the week, pull it into Team-Practices (This-Week). What could be nice is if we set up an additional column on the Team-Practices board call 'For this week' or something - we would then move stuff out of our 'backlog' column into the 'for this week' column, and then automagically have the tasks added to 'for this week' show up in the Team-Practices (This-Week) board. Is it possible to set a Herald rule to do this (when a task gets moved to a specific column, it gets added to another project)?

Is it currently convention to have tasks in a parent project as well as in a specific sprint?

I don't think there are conventions. https://www.mediawiki.org/wiki/Phabricator/Project_management#Sprints does not mention anything. Gather removes tasks from the parent project (T90990#1095651); LanguageEngineering does not seem to do so in their #LE-Sprint-XX projects.
Might be something to discuss on teampractices@ ?

Is it possible to set a Herald rule to do this (when a task gets moved to a specific column, it gets added to another project)?

No. See Herald's available options in T630#1131896 (I just added a screenshot there).