glab
glab copied to clipboard
profclems
Feature: Implement `issue --assignee @nobody`
Describe the feature or problem you'd like to solve As a developer, I would like to find issues which are not assigned to anyone so that I can pick up new issues
Propose a Solution
glab issue --assignee @nobody should find issues with no assignee, by analogy with https://github.com/profclems/glab/issues/483
Additional context
I have tried --not-assignee somebody --not-assignee somebodyelse and they don't seem to combine; the last one takes precedence.
The search which produces this result is glab api /projects/:id/issues/?assignee_id=None - would be great if we could just pipe that into glab issue list.
This issue has been automatically marked as stale because it has not had recent activity. We haven't had the time to address it yet, but we want to keep it open. This message is just a reminder for us to help triage issues.
Looking at the code structure, it seems to me it would be better to have something like glab issue list --unassigned, since the code is currently filtering issues by assignee using username, not id.
Hey, just looked at the go-gitlab package and we can't really set our AssigneeID to "None" cause it accepts only integers, as we can see here
Since I also would apreciate this feature, I've openned an issue at their repo so we can find a nice solution :)
Yeah, this is kinda dumb from GitLab's side.
The one thing we could do is filter the tests on our side, but I feel like that would be a lot of hassle, and pagination would painful. Lets wait and see If the go-gitlab issue brings some clarity on how we could deal with this, if not then we will have to do the filtering on our end.
Hey, just a small update about this So, they've updated the go-gitlab repo with something that will help us implment this, but we would have to pump up to this latest version, which would come with quite a lotta stuff to fix within the code, mostly types and stuff, so... It would be quite the PR
I have actually opened a PR for this at #982
It still needs to be tested before merging, because of those nasty breaking changes, but after we do this, we can implement this feature
This issue has been automatically marked as stale because it has not had recent activity. We haven't had the time to address it yet, but we want to keep it open. This message is just a reminder for us to help triage issues.