Fix GraphQL Boards labels setting
What does this MR do?
This MR fixes a bug that was present on GraphQL issue boards: when setting labels to issue A and clicking on the card of issue B, the updated labels are applied to the issue B. In the current MR, we add a watcher to "store" the current issue id and apply the labels correctly. This solution is a bit hacky, the proper fix will be a part of &6092 (closed)
Screenshots or Screencasts (strongly suggested)
How to setup and validate locally (strongly suggested)
Note make sure that :graphql_board_lists is enabled
- Go to issue boards/epic boards
- Select an issue
- Select a label (don't off click yet)
- Off click onto another issue
- Labels should be applied correctly to the first issue
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Related issue: #334465 (closed)
Edited by Natalia Tepluhina