post-resolution issue changes + add status category

fivetran-jamie commented 3 years ago

What change(s) does this PR introduce?

Allows for resolved issues that are updated after being resolved to have these changes reflected in daily history models
add status category
add incremental configs for Databricks -> the bulk of circle ci work is being done in https://github.com/fivetran/dbt_jira/pull/31https://github.com/fivetran/dbt_jira/pull/31

Does this PR introduce a breaking change?

[ ] Yes (please provide breaking change details below.)
[x] No (please provide explanation how the change is non breaking below.)

Is this PR in response to a previously created Issue

[x] Yes, Issue https://github.com/fivetran/dbt_jira/issues/29 and https://github.com/fivetran/dbt_jira/issues/22 (just the status category part -- versions will be in another PR or later in this PR...)
[ ] No

How did you test the PR changes?

- [x] CircleCi - [ ] Other (please provide additional testing details below) Also did a lot of running a full refresh with the old code, adding the new code, doing an incremental run with the new code (also with the old to compare), seeing if the missing days got backfilled **Select which warehouse(s) were used to test the PR** - [x] BigQuery - [x] Redshift - [x] Snowflake - [ ] Postgres - [ ] Databricks - [ ] Other (provide details below) **Provide an emoji that best describes your current mood** 🏓 **Feedback** We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your [feedback](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.

fivetran-jamie commented 3 years ago

@fivetran-joemarkiewicz would like to talk this though a little in standup

fivetran-jamie commented 3 years ago

moving postgres + spark compatibility to a different PR since the customer will hopefully be trying this branch out to test the calendar spine stuff (and it was the same person who wants status_category and versions added, so combining these two tasks here)

fivetran-jamie commented 3 years ago

todo: add version logic here -- it's a little more complicated than i thought since versions are a multiselect issue-field

fivetran-jamie commented 3 years ago

[ ] reminder to myself to re-generate documentation before merging

fivetran / dbt_jira

post-resolution issue changes + add status category #30