yetibot.api.jira — yetibot 20260320.131803.53157e2

Interface with a configured JIRA instance. Note: there are slight differences between server instances and JIRA Cloud, so some features may not be fully compatible. In most cases these functions were developed against a JIRA Enterprise instance.

To view all versions of the JIRA Rest API (and to suddelyl feel like you're living in the 90s), visit: https://docs.atlassian.com/software/jira/docs/api/REST/

This listing doesn't seem up to date as https://docs.atlassian.com/software/jira/docs/api/REST/8.5.3/ exists but is not in the listing.

Safest choice might be to develop against latest of Server REST API: https://docs.atlassian.com/software/jira/docs/api/REST/latest/

Hopefully someday they unify the cloud and enterprise APIs.

*jira-project* clj

Settings for the current channel, bound by yetibot.commands.jira

*jira-projects* clj

Settings for the current channel, bound by yetibot.commands.jira

access-token-url clj

add-worklog-item clj

(add-worklog-item issue-key time-spent work-description)

all-components clj

api-uri clj

(api-uri)

auth clj

authorize-url clj

base-uri clj

(base-uri)

channel-projects clj

(channel-projects channel-settings)

Retrieve the list of configured projects for a channel, given its settings

client-opts clj

(client-opts uri http-method & [query-params])

For oauth1 client-opts need to be computed for every API in order to generate an authz header, baking any query-params into the signature.

http-method should be: :GET :POST :PUT or :DELETE

cloud? clj

(cloud?)

Whether or not to use Cloud REST API calls: https://developer.atlassian.com/cloud/jira/platform/rest/v2/#api-group-User-search

components clj

(components project-key)

config clj

(config)

configured? clj

(configured?)

consumer clj

create-issue clj

(create-issue
  {:keys [summary component-ids reporter assignee priority-key desc project-key
          fix-version timetracking issue-type-id parent]
   :or {desc ""
        assignee "-1"
        issue-type-id
          (if parent (sub-task-issue-type-id) (default-issue-type-id))
        project-key (or (first *jira-projects*) (default-project-key))}})

This thing is a beast; thanks JIRA.

date-time-format clj

default-issue-type-id clj

(default-issue-type-id)

default-project clj

(default-project)

default-project-key clj

(default-project-key)

default-version-id clj

(default-version-id project-key)

delete-issue clj

(delete-issue issue-key)

endpoint clj

(endpoint & fmt-with-args)

fetch-and-format-issue-short clj

find-component-like clj

(find-component-like pattern-str)

Match components across all projects

find-priority-by-key clj

(find-priority-by-key k)

find-project clj

(find-project pk)

find-transition clj

(find-transition issue-key query)

Use regex to find by partial match on transition name

format-attachment-item clj

(format-attachment-item a)

format-attachments clj

(format-attachments issue-data)

format-comment clj

(format-comment c)

format-issue clj

(format-issue issue-data)

format-issue-long clj

(format-issue-long issue-data)

Show the full details for an issue

format-issue-short clj

(format-issue-short issue-data)

format-project clj

(format-project {{project-category-name :name} :projectCategory
                 project-key :key
                 project-name :name
                 :as project})

format-subtasks clj

(format-subtasks {{subtasks :subtasks} :fields})

format-worklog-item clj

(format-worklog-item w)

format-worklog-items clj

(format-worklog-items issue-data)

get-issue clj

(get-issue i)

Fetch json for a given JIRA

get-projects clj

(get-projects & [query])

get-transitions clj

(get-transitions i)

get-users clj

(get-users project)

http-delete clj

(http-delete uri & [{:keys [query-params] :as opts}])

http-get clj

(http-get uri & [{:keys [query-params] :as opts}])

http-post clj

(http-post uri & [{:keys [query-params] :as opts}])

http-put clj

(http-put uri & [{:keys [query-params] :as opts}])

issue-create-meta clj

(issue-create-meta)

issue-types clj

(issue-types)

jira-project-setting-key clj

This key is used to store channel-specific JIRA projects

max-results clj

(max-results)

oauth1 clj

parse-and-format-date-string clj

(parse-and-format-date-string date-string)

post-comment clj

(post-comment issue-key body)

priorities clj

(priorities)

project-for-key clj

(project-for-key k)

project-keys clj

(project-keys)

project-keys-str clj

(project-keys-str)

projects clj

(projects)

recent clj

(recent & [project])

request-token-url clj

resolve-issue clj

(resolve-issue i comment)

Transition an issue to the resolved state. If it is unable to make that transition nil will be returned

resolve-user-by-query clj

(resolve-user-by-query user-query)

Given a query representing a user return the first match, if any

search clj

(search jql)

search-by-query clj

(search-by-query query)

search-in-projects clj

(search-in-projects jql)

search-users clj

(search-users query)

Find a user entity matching against display name and email.

query - A query string that is matched against user attributes ( displayName, and emailAddress) to find relevant users. The string can match the prefix of the attribute's value. For example, query=john matches a user with a displayName of John Smith and a user with an emailAddress of [e-mail]

sub-task-issue-type-id clj

(sub-task-issue-type-id)

transition-issue clj

(transition-issue i transition-id & iss-comment)

update-issue clj

(update-issue issue-key
              {:keys [fix-version summary component-ids reporter assignee
                      priority-key desc timetracking]})

url-from-key clj

(url-from-key k)

user-ref clj

(user-ref assignee-user)

Jira Cloud and Server take different params when referencing users. Abstract the diff with this function

versions clj

(versions)

(versions project-key)