-
Notifications
You must be signed in to change notification settings - Fork 328
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
save queries in configuration file #99
Comments
Ok, it looks like we couldn't use -Q for this, because it is already used for --quiet. |
Something like the following works for me to allow usage like
|
I am looking for a convenient way to list all tickets assigned to me that are not resolved. How do you suggest doing this? Thanks much, William |
Here's an abbreviated and redacted version of what I have, which allows me to run
I find it works quite well. |
I have created an example for how to create It no longer uses the executable config file, but that mechanism should still work. Still thinking named queries might be useful also, perhaps something like:
Then modify the list/edit usage to access the via:
|
Added named queries into
They can be templates and can use command line options and configs to populate:
|
Changed released here: https://github.com/Netflix-Skunkworks/go-jira/releases/tag/v1.0.6 |
My co-worker and I cane up with another possible enhancement to this tool.
The -q option allows jql on the command line. It would be cool if there were a way to save jql queries in .jira.d and refer to them by name on the command line.
We could use a command line option, for example -Q (note upper case) to refer to a query like this:
I thought about saving the queries themselves in config.yml, but I'm not sure if that would work or what the syntax would be. My thought is a "queries" dictionary in which the key is the name and the value is the jql query itself, but I'm not quite sure what that would look like.
What are your thoughts about something like this? If you give me the information, I may look into submitting a pull request for this.
Thanks,
William
The text was updated successfully, but these errors were encountered: