Add parent_id field in the field_option table

[sergiisolaa]

Pull Request
Are you a current Fivetran customer?
Sergi Solà - Data Analytics Engineer - Wallbox Chargers

What change(s) does this PR introduce?

Add parent_id field in the field_option table. The field is used when defining custom fields as parent and child custom fields can be created to define some main categories and subcategories.

Did you update the CHANGELOG?

• Yes

Does this PR introduce a breaking change?

• Yes (please provide breaking change details below.)
• No (please provide an explanation as to how the change is non-breaking below.)

It does not introduce a breaking change in the package as we are only introducing one new field in a table, from which no other table depends in the package.

Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

• Yes

Is this PR in response to a previously created Bug or Feature Request

• Yes, Issue/Feature [link bug/feature number here] --> FEATURE - Add parent_id field to stg_jira__field_option #31
• No

How did you test the PR changes?

• CircleCi
• Local (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

• BigQuery
• Redshift
• 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 on our existing dbt packages or what you'd like to see next.

[fivetran-joemarkiewicz]

@sergiisolaa thank you so much for opening this PR! 🏅

The updates you made looked great and worked on my end. I also tested to ensure the new field wouldn't impact the downstream dbt_jira model, and we look good to go!

I did make a few minor edits to your PR to update our hosted documentation with the changes you applied. I also added the new field to our get_field_option_columns macro so users who do not have this field are still able to use the package successfully.

With that, we are good to go and I will approve this PR! Thanks again for this contribution back to the open source package 😄 You can expect the official release later today.