Resolve "API naming for issue scope"
What does this MR do?
Add API issue scope created_by_me and assigned_to_me and update doc
Are there points in the code the reviewer needs to double check?
If any form of deprecation warning is required.
Why was this MR needed?
To replace respective created-by-me and assigned-to-me scope which are kebab-cased.
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-and-qamanual pipeline job)
What are the relevant issue numbers?
Closes #44799 (closed)
Merge request reports
Activity
marked the checklist item Changelog entry added, if necessary as completed
marked the checklist item Conform by the style guides as completed
assigned to @jprovaznik
Thanks @lulalala, I left couple of comments inline. Overall it looks great!
assigned to @lulalala
@lulalala Please add labels to your merge request, this helps triage community merge requests and is generally good for good organization. Thanks!
added Deliverable Plan [DEPRECATED] api backend breaking change ~2975006 issues labels
@rymai ah thanks for reminding. I completely missed that page when I was reading through the handbook :P
added 2 commits
added 1 commit
- 1f93a829 - Change to allow legacy only on controller level
