wusanny

**Issue description** Hello, we have a client who is using elementary dbt package in dbt Cloud and reported that they are not getting a value returned for the `job_name` column...

Understanding how elementary resolves dbt models with CI jobs

1

**Describe the bug** _Uncertain if this is a bug or expected behaviour, but we are quite confused with the current behaviour, thus raising this issue to get further clarification._ We...

Executing 'dbt docs generate' when the 'where' clause has different combinations of schemas > produces a permission error

3

### Expected behavior When we execute `dbt docs generate` on sources that are located in different schemas - we should be able to access them from the different schemas with...

## Overview Our customer has an on-run-end in their dbt_project.yml as follows: ``` on-run-end: - "{% if target.name == 'prod' or target.name == 'test' %}{{ dbt_artifacts.upload_results(results) }}{% endif %}" ```...

Error associated with `persist_docs` and schema definitions inconsistent with actual built models - present in dbt v1.6 but NOT v1.7 and up

2

### Describe the bug An error message that used to show up in dbt v1.6 (when certain conditions are met), no longer shows up in dbt v1.7 and above. In...