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
Is your feature request related to a problem? Please describe.
When creating a new issue or PR and you want to add it to be tracked by an Epic or similar, if it wasn't created inside the tracker, you need to go back to it and add the newly created issue/PR to the tasklist.
Describe the solution you'd like
We should implement a GHA that looks for Tracked By in the same way GitHub does for Closed By. When it finds Tracked By it should add the issue to the tracker issue in a tasklist in one of two ways:
If there's already a tasklist that doesn't have a custom title, add it to the existing tasklist
If there's no tasklist or one with a custom title, create a new tasklist
We don't want to add an issue to an existing tasklist with a custom name because we don't know if the newly created link makes sense there. It's easy enough to drag/drop the issues around inside tasklists after creation
Describe alternatives you've considered
No response
Additional context
This should continue the streamlining process to make it as easy as possible to do thorough project tracking. This request is a precursor to another similar, but more complicated action - adding Blocked By.
The text was updated successfully, but these errors were encountered:
Is this a duplicate?
Area
Infrastructure
Is your feature request related to a problem? Please describe.
When creating a new issue or PR and you want to add it to be tracked by an Epic or similar, if it wasn't created inside the tracker, you need to go back to it and add the newly created issue/PR to the tasklist.
Describe the solution you'd like
We should implement a GHA that looks for
Tracked By
in the same way GitHub does forClosed By
. When it findsTracked By
it should add the issue to the tracker issue in a tasklist in one of two ways:Describe alternatives you've considered
No response
Additional context
This should continue the streamlining process to make it as easy as possible to do thorough project tracking. This request is a precursor to another similar, but more complicated action - adding
Blocked By
.The text was updated successfully, but these errors were encountered: