yetibot.commands.jira — yetibot 20260214.001036.92bc408

assign-cmd clj

(assign-cmd {[_ iss-key assignee] :match settings :settings})

jira assign <issue> <assignee> # assign <issue> to <assignee>

bar clj

(bar x)

override1

comment-cmd clj

(comment-cmd {[_ iss-key body] :match user :user settings :settings})

jira comment <issue> <comment> # comment on <issue>

components-cmd clj

(components-cmd {:keys [settings]})

jira components # list components and their leads by project

configured-projects-cmd clj

(configured-projects-cmd {:keys [settings]})

jira configured-projects # list configured projects (⭐️ indicates global default; ⚡️ indicates channel default; channel default overrides global default)

create-cmd clj

(create-cmd {[_ opts-str] :match settings :settings})

jira create <summary> [options] # creates a new JIRA issue.

 Whether `options` are optional or not depend on your JIRA Project
 configuration. For example, sometimes `description` is required.

 Options are:

-j, --project-key PROJECT KEY Project key (use channel set jira-project PROJECT1 to set a channel-specific default) -c, --component COMPONENT Component -i, --issue-type ISSUE TYPE Issue type -s, --summary SUMMARY Summary -a, --assignee ASSIGNEE Assignee -e, --reporter REPORTER Reporter -f, --fix-version FIX VERSION Fix version -d, --desc DESCRIPTION Description -t, --time TIME ESTIAMTED Time estimated -r, --remaining REMAINING TIME ESTIAMTED Remaining time estimated -p, --parent PARENT ISSUE KEY Parent issue key; creates a sub-task if specified -y, --priority PRIORITY Priority of the issue

delete-cmd clj

(delete-cmd {[_ issue-key] :match})

jira delete <issue> # delete the issue

foo clj

format-error clj

(format-error {:keys [status body]})

format-version clj

(format-version v)

issue-opts clj

issue-types-cmd clj

(issue-types-cmd {[_ issue-types-filter] :match})

jira issue-types [<name to match>] # return issue types, optionally filtering on <name to match>

jql-cmd clj

(jql-cmd {[_ jql] :match settings :settings})

jira jql <jql> # return up to 15 issues matching <jql> query across all configured projects

parse-cmd clj

(parse-cmd {[_ text] :match})

jira parse <text> # parse the issue key out of a jira issue URL

parse-issue-opts clj

(parse-issue-opts opts)

Parse opts using issue-opts and trim all the values of the keys in options

priorities-cmd clj

(priorities-cmd {:keys [settings]})

jira priorities # list JIRA priorities

project-users-cmd clj

(project-users-cmd {:keys [settings] [_ project-key] :match})

jira project-users # list the users channel project or default project jira project-users <project> # list the users for the configured project(s)

projects-cmd clj

(projects-cmd {[_ query] :match})

jira projects [<query>] - list projects, optionally matching <query>

recent-cmd clj

(recent-cmd {[_ project] :match :keys [settings] :as cmd-opts})

jira recent # show the 15 most recent issues from default project(s) jira recent <project> # show the 15 most recent issues for <project>

report-if-error clj

(report-if-error req-fn succ-fn)

Checks the stauts of the HTTP response for 2xx, and if not, looks in the body for :errorMessages or :errors. To use this, make sure to use the :throw-exceptions false, :content-type :json and, :coerce :always options in the HTTP request.

resolve-cmd clj

(resolve-cmd {[_ iss comment] :match user :user settings :settings})

jira resolve <issue> <comment> # resolve an issue and set its resolution to fixed

search-cmd clj

(search-cmd {[_ query] :match settings :settings})

jira search <query> # return up to 15 issues matching <query> across all configured projects

show-cmd clj

(show-cmd {[_ issue-key] :match})

jira show <issue> # show the full details of an issue

success? clj

(success? res)

transition-cmd clj

(transition-cmd {[_ issue-key transition-name] :match})

jira transition <issue> <transition> # Move <issue> through <transition>

transitions-cmd clj

(transitions-cmd {[_ issue-key] :match})

jira transitions <issue> # list the available transitions for <issue>

update-cmd clj

(update-cmd {[_ issue-key opts-str] :match settings :settings})

jira update <issue-key> [options] # update an existing JIRA issue

 Available `options` are:

-j, --project-key PROJECT KEY Project key (use channel set jira-project PROJECT1 to set a channel-specific default) -c, --component COMPONENT Component -i, --issue-type ISSUE TYPE Issue type -s, --summary SUMMARY Summary -a, --assignee ASSIGNEE Assignee -e, --reporter REPORTER Reporter -f, --fix-version FIX VERSION Fix version -d, --desc DESCRIPTION Description -t, --time TIME ESTIAMTED Time estimated -r, --remaining REMAINING TIME ESTIAMTED Remaining time estimated -p, --parent PARENT ISSUE KEY Parent issue key; creates a sub-task if specified -y, --priority PRIORITY Priority of the issue

users-cmd clj

(users-cmd {[_ query] :match})

jira users <query> # search for users matching <query>

versions-cmd clj

(versions-cmd {[_ project-key] :match settings :settings})

jira versions <project-key> # list versions for <project-key> jira versions # Lists versions for all configured project-keys

worklog-cmd clj

(worklog-cmd {[_ issue-key time-spent work-description] :match})

jira worklog <issue> <time-spent> <work-description> # log work on <issue>