Open elementljarredc opened 11 months ago
Hey folks,
We talked through this in the Core / UI meeting today:
We could expose the run tags of the job on the jobs page and allow you to filter based on the run tags. (Run tags are the tags you define on your job which are applied to each run of the job automatically).
This seems like a stopgap measure, and would likely just lead to more questions. Jobs would have tag filtering but sensors/schedules would not which might feel odd.
Run tags are currently static, but this would prevent us from ever making them dynamic / derived from a function.
Instead of going with this stop-gap solution, we want to think about this more broadly as part of an I/A iteration. Going to put this into @braunjj's mind palace for now :)
Kraft Heinz team has a pattern of initiating runs from the jobs page, and uses tags to track their jobs.
This is also related to their request to be able to bulk run jobs from the jobs page, the workflow they'd like to follow is:
Snippet from gong regarding the Job level tagging
[https://us-91031.app.gong.io/call?id=5653838001402112485&highlights=[{"type"%3A"SHARE"%2C"from"%3A307%2C"to"%3A554}]](https://us-91031.app.gong.io/call?id=5653838001402112485&highlights=%5B%7B%22type%22%3A%22SHARE%22%2C%22from%22%3A307%2C%22to%22%3A554%7D%5D)