@ebaque I'm assigning you here for review and weighing. Note that the description is quiet short, it'll require some investigation into the previous closed issue. If you find that this is all frontend work then we can defer to @rhardarson or someone with more FE experience here.
Note: As we may apply the same flow as the Project members search, no autocomplete seems to be involved in this work. No API endpoint to update/create then.
Hello @astoicescu I assigned this issue to myself but then that you were working on a related (potentially blocking?) MR: !45382 (merged)
Can you please confirm that I can start working on the backend of this issue here? Or are there any backend code you're planning to add, and therefore I should wait until you merge them in?
Hey, @ebaque! I think you can start working on this as long as you base your branch on the one pertaining to this MR: !45382 (merged) . I'm 99% sure there won't be anymore backend changes, as I only have to address the frontend maintainer review now.
@esybrant@amandarueda I have a question re. the current proposal: what type should it be?
In the backendMR that I'm currently working on I'm implementing an "exact term" search.
Please let me know if you're thinking that we should implement another type of search, and I will take care of it in another MR
I reused some of the logic used in the screenshot above, for consistency sake. Until now, I thought the group member search was using "exact term" search, but after trying again, it turns out that "partial term" search works if the searched string is at least 3 character long (TIL).
@astoicescu since you've been working on the new group billable user page and are familiar with its Vue components, and since the backend MR for this issue is being reviewed (soon ready to be merged in), could you please take over the frontend part of this issue, if you have any availability?
@astoicescu - In !50702 (merged) I added to the GitLab.com "Subscriptions" page. Since we're adding a search capability to the Seat usage UI page I think we should create a docs page just for this UI. Either that or create a new section to the GitLab.com subscriptions documentation.
I'm happy to help with the documentation work. I would prefer the docs changes be included with the feature's MR. If the feature needs to be reverted, the documentation will be reverted with it.