feature/custom-field-mapping update

[fivetran-joemarkiewicz]

Are you a current Fivetran customer?

Fivetran created PR

What change(s) does this PR introduce?

Previously the jira__daily_field_history and jira__issue_enhanced models allowed for users to leverage the issue_field_history_columns to bring through custom field_ids. However, the field_id was not very intuitive to report off. Therefore, the package has been updated to bring through the field_name values in the variable and persist through to the final models.

Did you update the CHANGELOG?

• [X] Yes

Does this PR introduce a breaking change?

• [X] Yes (please provide breaking change details below.)
• [ ] No (please provide an explanation as to how the change is non-breaking below.) This changes the functionality of a variable and will cause a breaking change for existing users.

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)

• [X] Yes

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

• [X] Yes, Issue/Feature #53
• [ ] No

How did you test the PR changes?

• [X] CircleCi
• [X] Local (please provide additional testing details below)

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

• [X] BigQuery
• [X] Redshift
• [X] Snowflake
• [X] 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-joemarkiewicz]

This can be tested using the following configuration:

packages:
  - git: https://github.com/fivetran/dbt_jira.git
    revision: feature/custom-field-mapping
    warn-unpinned: false