Swimlanes - Add issue to list
What does this MR do?
When issues are fetched using GraphQL (as in Swimlanes), adding issue to a list requires a VueX action. This currently uses the existing REST API endpoint as create issue GraphQl mutation is not yet available.
Feature flag :boards_with_swimlanes is required to test this feature.
| Iteration | Link |
|---|---|
| Iteration 1 | !32739 (merged) |
| Iteration 2 | !33469 (merged) |
| Iteration 3 | !33909 (merged) |
| Iteration 4 | !34366 (merged) |
| Iteration 5 | !35490 (merged) |
| Iteration 6 | !36016 (merged) |
| Iteration 7 | !38258 (merged) |
| Iteration 8 | !39054 (merged) |
| Iteration 9 | !39183 (merged) |
| Iteration 10 | !40221 (merged) |
| Iteration 11 | !40344 (merged) |
| Iteration 12 | !41542 (merged) |
| Iteration 13 | Current MR |
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Florie Guibert