Creating an issue should add board scope to it
Summary
The new issue boards implementation on GitLab.com appears to have regressed this previously added feature: #287713 (closed)
Specifically, the milestone attribute from the active board scope configuration is no longer set on the issues created through GraphQL.
Issues are created without the milestone attribute set on them, requiring users to edit the issue and set the milestone each time.
Steps to reproduce
- Visit a group's issue boards page
- Click edit board to set a scope
- Set scope for milestone as some pre-created milestone
- Save, and then click the + icon to create a new open issue
- Fill issue details, and save to create the issue
- Here's the regression bit:
Current behavior: Click the added issue, and it shows no value in its Milestone field. Scope was not copied.
Previous behavior (checked in 14.0 self-managed instance): Click the added issue, and it shows the scoped milestone pre-set on it.
Example Project
https://gitlab.com/groups/gitlab-gold/hchouraria/-/boards/2944864?milestone_title=hch%20nxt
What is the current bug behavior?
Newly created issues using the board's
What is the expected correct behavior?
Newly created issues using the board's
Relevant logs and/or screenshots
Set scope to a milestone:
Create an issue:
Created issue has no milestone:
Output of checks
This bug happens on GitLab.com