InitIssueWithMetaAndFields - should set IssueFields.Project and IssueFields.Type from MetaProject/MetaIssueType

[ArcticSnowman]

Is your feature request related to a problem? Please describe.

InitIssueWithMetaAndFields current does not set the Issue.IssuesField.Project or Issue.IssueFields.Type, The passed in MetaProject and MetaIssueType only server to define a list of field translations. They don't set the Project or Type.

Describe the solution you'd like

InitIssueWithMetaAndFields - should set the those fields from the Meta information that was passed in.

Seems overly complex to require the user to set those explicitly after having passed in the meta data.

[github-actions]

Hi! Thank you for taking the time to create your first issue! Really cool to see you here for the first time. Please give us a bit of time to review it.

[andygrunwald]

Hey,

I am very sorry that this issue has been open for a long time with no final solution. We work on this project in our spare time, and sometimes, other priorities take over. This is the typical open source dilemma.

However, there is news: We are kicking off v2 of this library 🚀

To provide visibility, we created the Road to v2 Milestone and calling for your feedback in #489

The development will take some time; however, I hope you can benefit from the changes.
If you seek priority development for your issue + you like to sponsor it, please contact me.

What does this mean for my issue?

We will work on this issue indirectly.
This means that during the development phase, we aim to tackle it.
Maybe in a different way like it is currently handled.
Please understand that this will take a while because we are running this in our spare time.

Final words

Thanks for using this library.
If there is anything else you would like to tell us, let us know!