To set up a singular (custom SQL) test with an owner in Elementary, you can add the owner in the

meta

section of the test's

config

block, like this:

jinja {{ config(     meta={         "owner": "@your.slack.handle"     } ) }}  -- your test query here

However, currently, Elementary does not support filtering by test-level owners in the dashboard or report. The owner field in the dashboard is only populated if the owner is set at the model level, not at the test level. This is a known limitation: even if you set the owner in the test's

meta

, the test will still show as "no owner" when filtering by owner in the Elementary dashboard. The owner meta will appear in the metadata, but not in the owner filter or alert tagging for singular tests. Workarounds: - If your singular test references a model (using

ref()

), you can set the owner on that model. The test will then inherit the owner from the model, and filtering by owner in the dashboard will work as expected. - If your test depends on multiple models, Elementary currently does not support owner tagging for such tests, as it expects a one-to-one relationship between a test and a model. References: - [Singular test owner meta not supported for dashboard filtering](https://slack.com/archives/C02CTC89LAX/p1700208196154229) - [Owner meta in test config is not picked up for dashboard filtering](https://slack.com/archives/C02CTC89LAX/p1667915416294299) - [Workaround: set owner on referenced model](https://slack.com/archives/C02CTC89LAX/p1700208196154229) Summary: You can set the owner in the test's

meta

, but for the owner to appear in the dashboard filter, you must set it on the referenced model. Test-level owner meta is not currently supported for dashboard filtering or alert tagging in Elementary.

@kapa.ai As I mentioned, adding the owner in the

meta

section of the

config

block does not always work. In many cases, my tests are still showing up as "no owner" in the Elementary dashboard.

You are correct—adding the owner in the

meta

section of the

config

block for a singular (custom SQL) test does not always result in the owner being displayed in the Elementary dashboard. This is a known limitation in Elementary. Key points from the knowledge sources: - The Elementary dashboard currently only supports filtering by owners set at the model level, not at the test (singular test) level. Even if you set the owner in the test's

meta

, the dashboard will show "no owner" for that test when filtering by owner. The owner information is stored in the metadata, but it is not surfaced in the dashboard's owner filter or in alert tagging for singular tests [see discussion](https://slack.com/archives/C02CTC89LAX/p1700208196154229) [another example](https://slack.com/archives/C02CTC89LAX/p1667915416294299). - If your singular test references a model (using

ref()

), and that model has an owner set in its

meta

, the test will inherit the owner from the model. This is currently the only way to have the owner show up in the dashboard filter for singular tests. If the test depends on multiple models, Elementary does not support owner tagging for such tests, as it expects a one-to-one relationship between a test and a model [see explanation](https://slack.com/archives/C02CTC89LAX/p1700208196154229). - This limitation has been acknowledged by the Elementary team, and there are plans to address it in the future, but as of now, there is no way to have the owner set at the test level appear in the dashboard filter or alert tagging for singular tests. Summary: Setting the owner in the

meta

section of a singular test's config block does not make the owner appear in the Elementary dashboard's owner filter. Only owners set at the model level are currently supported for this feature. This is a known product limitation.