Anwar Hidayat

**Description** This issue is included in [this discussion](https://github.com/odpf/optimus/discussions/479). Under job service and priority resolver, there's a duplicated `populateDownstreamDAGs` in job/service.go is too tied up with Airflow scheduler. The logic itself...

**Description** This issue is part of [this discussion](https://github.com/odpf/optimus/discussions/479). The current (03952e961d54da33aa8daafda45e1d5d3d132d30) job service implementation handles a lot of things, like: * job spec operation * job run creation * job...

**Description** This issue is part of [this discussion](https://github.com/odpf/optimus/discussions/479). There are two issues in the mechanism when we want to get upstream resource urn: * we require the whole project spec...

**Description** This is part of [this discussion](https://github.com/odpf/optimus/discussions/479). `PrepareJobSpecMap` is being used by Replay, ReplayDryRun, and Backup to get the lineage of the requested job. This is not necessary, too complex,...

**Description** If we check the current implementation of job spec repository (referring implementation until 516c9cd72e509cd740eca7b2a342f066a67ca287), there are some repositories where we can do some operations on job spec. This could...

**Describe the bug** This bug happens when we want to create one or more sensors that already exist. So far, this bug happens when we encounter the following scenario: *...

**Description** With this feature, the user could define the number of retry and the number of time out in their job spec. This allows more flexibility to the user, especially...

This update is part of [this issue](https://github.com/odpf/optimus/issues/417) in Optimus. This is to create a Kubernetes job that allows rollback feature.