Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow specifying multiple statuses #6

Closed
chx opened this issue May 30, 2021 · 2 comments · Fixed by #12
Closed

Allow specifying multiple statuses #6

chx opened this issue May 30, 2021 · 2 comments · Fixed by #12

Comments

@chx
Copy link

chx commented May 30, 2021

When listing my issues, it'd be helpful to be able to filter on "New Request,In Review,To Do" or some other similar syntax.

Note I was able to do jira-terminal list -j 'assignee = "chx@example.com" AND status != "Closed"' so this issue is low priority, I guess.

amritghimire added a commit that referenced this issue May 31, 2021
For the list subcommand, multiple filters are already available.

Closes #6
amritghimire added a commit that referenced this issue May 31, 2021
For the list subcommand, multiple filters are already available.

Closes #6
@chx
Copy link
Author

chx commented Jun 1, 2021

Thanks so much for the rapid progress.

After the commit I tried more things and found jira-terminal list -S 'In Progress' 'To Do' 'New Request' to work for multiple . I am not sure whether this is intentional or some JQL weirdness but ... it's amazing! :)

@jetm
Copy link

jetm commented Jul 5, 2023

@amritghimire Is it possible to pass a negation to the status name to list the other issues?
There is case where it would be shorter to write something like this: jira-terminal list -S "~Closed" to list all issues are not closed, instead of writing all the possible statuses. I know is possible to write a query, but it will be nice to supported it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants