v0.16.0 dbt_jira

PR #122 contains the following updates:

🚨 Breaking Changes: Bug Fixes 🚨

• The following fields in the below mentioned models have been converted to a string datatype (previously integer) to ensure classic Jira projects may link issues to epics. In classic Jira projects the epic reference is in a hyperlink form (ie. "https://ulr-here/epic-key") as opposed to an ID. As such, a string datatype is needed to successfully link issues to epics. If you are referencing these fields downstream, be sure to make any changes to account for the new datatype.
  • revised_parent_issue_id field within the int_jira__issue_type_parents model
  • parent_issue_id field within the jira__issue_enhanced model

Documentation updates

• Update README to highlight requirements for using custom fields with the issue_field_history_columns variable.

Under the Hood

• Included auto-releaser GitHub Actions workflow to automate future releases.
• Updated the maintainer PR template to resemble the most up to date format.
• Updated field and issue_field_history seed files to ensure we have an updated test case to capture the epic-link scenario for classic Jira environments.

Full Changelog: v0.15.0...v0.16.0