I'm seeing lots of bugs created under the current sprint but not being tagged with Gather
I'm not sure if this is problematic but if it is we should solve it by making sprints have an associated project that bugs also get tagged with.
We can't rely on humans to tag with both. One month into using Phabricator sprints and I do not see this problem going away.
This can be done, but while T630: Enabling Herald is not solved, an admin will need to set up this Herald rule for you.
Generally: Herald allows this (see screenshot in T630#1131896) and this could be set up if wanted.
For Gather specifically I am not sure this is wanted, see T90990#1095651.
I don't think there are general conventions either (see my comment in T91322#1132032) so feel free to bring this up both on Gather team level and/or on a global level (teampractices@?).
Herald rules are run on every change to every task. With the current number of herald rules we are already experiencing significant delays to each task edit. The proliferation of herald rules is going to be a problem soon.
You'd have to setup a herald rule for every newly created sprint and that doesn't seem feasible.
If you could create sub projects then that might fix things (every task in a sub project gets also added to the parent project).
I think we have to just deal with the status quo. Herald rules don't sound like they scale.
@Jdlrobson: It might be possible to make a single herald rule that says "for every project that is a sprint, add the associated product project as well" but we'd need to know how to determine what is "the associated product project" dynamically rather than adding lots of herald rules.
I don't think there is currently a way to do that? Maybe by convention, I'm not sure.