Resolve "Bulk update due date of issues"
What does this MR do?
Add Bulk update due date of issues
Are there points in the code the reviewer needs to double check?
- I did not use
gl_dropdown
sincePikaday
stopclick
event propagate to parent. So I think it is less meaning to usegl_dropdown
- There is a situation that user may clear the due date. So I set the text as
No due date
- Function is ready but I will add tests later maybe in the next week
Why was this MR needed?
convenient for user to update a bundle of issues for due date
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
End-to-end tests pass ( package-qa
manual pipeline job)
What are the relevant issue numbers?
Closes #39609 (moved)
Edited by Ken Ding