FE: Allow users to edit labels of a Jira issue on details page
What does this MR do?
This MR adds the frontend (with mock backend) that allows editing of labels on the Jira issue details page. This is behind the feature flag jira_issue_details_edit_labels.
- Simple backend (mock) that allows the fetch labels for a certain issue.
- Reusing functionality from
labels_select_vueto allow editing of labels. This component takes care of fetching labels, frontend interactions and calling the right methods to update them once selection is done.
Screenshots (strongly suggested)
Jira issue labels edit video
Jira issue labels edit screenshots
| Initial | Loading | Selecting | Updating |
|---|---|---|---|
 |
 |
 |
 |
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.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
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
Related to #328787 (closed)
Edited by Justin Ho Tuan Duong