[Bug] Assignee names, reporter names, emails etc not appearing how they should

[jamienewcomb]

Is there an existing issue for this?

• [X] I have searched the existing issues

Describe the issue

This does not look right to me. Don't think this is a me issue but do say if it is

Relevant error log or model output

No response

Expected behavior

Would expect to see the information aligned to the column names

dbt Project configurations

-

Package versions

-

What database are you using dbt with?

snowflake

dbt Version

-

Additional Context

No response

Are you willing to open a PR to help address this issue?

• [ ] Yes.
• [ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
• [ ] No.

[fivetran-joemarkiewicz]

Hi @jamienewcomb can you confirm that in the source table for jira.user those fields do not look like that? The int_jira__issue_users model (which I believe is what you are querying from) populates these fields by performing a join on the source table. https://github.com/fivetran/dbt_jira/blob/78c49634ffa891b376eb2b1c2675d6a3ba3867ce/models/intermediate/int_jira__issue_users.sql#L29-L43

I wouldn't believe this should cause any data quality issues, but curious to see what you say it looks like at the source.

[jamienewcomb]

@fivetran-joemarkiewicz Yeah the source table JIRA_USER looks like this aswell.

Feels odd that all the personal information is jumbled up but the surrounding fields are absolutely fine with the correct info. The user IDs are all correct aswell

[jamienewcomb]

Could Atlassian have done something here - which is what I am thinking

[fivetran-joemarkiewicz]

Hi @jamienewcomb this may be a result of Snowflake column level hashing based on role permissions. You Snowflake admin may have restricted access to those columns based on the permissions of the role you are using.

I would reach out to your Snowflake admin and see if this is the case.

[jamienewcomb]

Thanks @fivetran-joemarkiewicz - that would make alot of sense. this feels like a me issue so gonna close for now while I check that and will reopen if we feel there is something else wrong