Add ability to set iteration on issue creation via GraphQL API
What does this MR do and why?
!70007 (merged) was reverted because it would always assign the first iteration found for a user to all newly created issues.
This MR reintroduces those changes plus the bug fix to prevent that.
Relates to #300897 (closed)
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #300897 (closed)