Sometimes a task is created on a component project/tag (TPG-Essential-Functions ) but not added to the unified backlog (Team-Practices ). Since the team only looks at the backlog and workboard (Team-Practices (This-Week) ), a task can get lost. This Herald would catch those tasks and auto-tag them with the backlog.

• It will not tag Team-Practices (This-Week) because that would circumvent SOP
  • It may also cause a conflict if a task is tagged with both a project and that same project's Milestone
• Team-Practices (This-Week) does not need to be one of the "straggler" projects because it is a Milestone of Team-Practices (it would need to be included if it was not a Milestone of the primary backlog)
  • It would also cause tasks that are added to Team-Practices (This-Week) to revert to Team-Practices (once), since they are technically 2 different projects
• The tags triggered would need to be changed, or at least added to, every quarter (technically, every time a new tag is created)
  • Related for future proofing: T144041: Develop a custom herald condition for maniphest tasks: "projects include any subprojects of ___ "