Initial support for search arguments #241
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
#238 should be fixed by this.
Adds arguments to the !jira search command!
There are two types of arguments that can be used with this, which are arguments that start with
:
and arguments that start with_
.Arguments starting with
:
are single-word arguments, and there's currently only one of these::query
. This argument allows users to use a JQL query that they write themself, instead of using the building blocks that the !jira search command provides. Example usage:!jira search :query text ~ crash AND reporter = markderickson
Arguments starting with
_
are multi-word arguments, and there are lots of these:_project
,_creator
,_reporter
,_assignee
,_version
,_fixversion
,_resolution
,_status
,_confirmation
,_gamemode
,_id
,_key
,_labels
,_priority
,_mp
,_comment
,_summary
,_description
,_environment
. Each one of these can be paired with a corresponding value to build onto the query. Using only multi-word arguments allows for usage of the command as it works currently. Example usage:!jira search _project MC _labels crash _reporter markderickson _mp "Very Important" _confirmation "Community Consensus" height limit crash 256
I will work on this once the bot is updated to discord.js version 13!