[Feature] Properly support multiple field selections in `daily_issue_field_history`

[fivetran-avinash]

Is there an existing feature request for this?

• I have searched the existing issues

Describe the Feature

There will be times when a Jira user will assign multiple field values to a particular issue (i.e. multiple components or sprints). Currently, the jira__daily_issue_field_history model does bring in values, but only the ids associated with those values.

In the example below, we've added multiple components and sprints to a particular issue, but could only bring in the ids into the model.

We should be able to support bringing in all field name values into our models so our customers can more easily understand the history of issues and all the various fields associated with it, day over day.

Describe alternatives you've considered

No response

Are you interested in contributing this feature?

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

Anything else?

No response

[fivetran-catfritz]

In this PR and this issue for dealing specifically with issue_type, it became apparent that this tends to apply to field types that have their own tables (reference ERD). This affects these fields:

• priority
• project
• resolution
• SLA

I don't think there are more, however it would be worth another pass comparing tables to fields.