Skip to content

feat: Add assignee filters for issue_list

John McAvoy requested to merge github/fork/j-mcavoy/168_list_issues_assigned_to_a_user into trunk

Description Adds issue list filtering for assignees

Unfiltered:

$ glab issue list       

Showing issues 10 of 10 on j-mcavoy/glab-test


IssueID Title                   Labels                  CreatedAt           
#11     This is my issue                                about 21 minutes ago
#10     Test test test          (dummy, mr test)        about 9 days ago    
#9      Dummy Issue             (dummmy)                about 9 days ago    
#8      Dumb dumb                                       about 9 days ago    
#7      Dummy Issue             (dummmy)                about 9 days ago    
#6      Dummy Issue             (dummmy)                about 9 days ago    
#5      My New 123 Issue                                about 10 days ago   
#4      NEw new                                         about 10 days ago   
#3      New Issue #2                                    about 10 days ago   
#2      My Issue                                        about 10 days ago

Filtered:

$ glab issue list --mine

Showing issues 1 of 1 on j-mcavoy/glab-test


IssueID Title                   Labels  CreatedAt           
#11     This is my issue                about 22 minutes ago
$ glab issue list --assignee j-mcavoy

Showing issues 1 of 1 on j-mcavoy/glab-test


IssueID Title                   Labels  CreatedAt           
#11     This is my issue                about 22 minutes ago

Related Issue

#168 (closed)

Motivation and Context

How Has This Been Tested?

I tested using my upstream fork of go-lab and using my test GitLab repo

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Merge request reports