You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issues created in this repo may not be visible to the REX team or triage process if they are not assigned to Project => Team REX. This means we may not prioritize or sequence tasks appropriately.
Issues that are assigned to REX are already moved to Awaiting Triage by GitHub automation.
How will we know when it's done?
New issues created in the opencodelists repo are automatically assigned to project Team REX and status Awaiting triage.
If successful, create a similar task in the job-server repo. Evangelize the idea to other Tech teams.
What are we doing?
This is available in the marketplace for example, or this.
I've added a workflow into the project, which seemed like it would do this. However, I can't restrict it to new items, so I've restricted it to things with the tech-support label (like we've done with job-server).
Why are we doing this?
Issues created in this repo may not be visible to the REX team or triage process if they are not assigned to
Project => Team REX
. This means we may not prioritize or sequence tasks appropriately.Issues that are assigned to REX are already moved to
Awaiting Triage
by GitHub automation.How will we know when it's done?
New issues created in the opencodelists repo are automatically assigned to project
Team REX
and statusAwaiting triage
.If successful, create a similar task in the job-server repo. Evangelize the idea to other Tech teams.
What are we doing?
This is available in the marketplace for example, or this.
Defining delivery tasks guidance
The text was updated successfully, but these errors were encountered: