Presentation on a Clojure-based tool for extracting SLA metrics (and any other metrics) from JIRA using its REST API. https://github.com/noahlz/cosla

1. Cosla:
JIRA SLA Tool in Clojure
Noah Zucker
@noahlz / nzucker@gmail.com

2. Cosla
Clojure-based command-line tool for
extracting SLA metrics from your JIRA
https://github.com/noahlz/cosla/
(SLA = Service Level Agreement)

3. Use Case: Project Bug KPIs
● Tickets open-per-day.
● Time-to-close tickets.
● Ticket average time-in-status.
Basically, minimalistic DIY alternative to
JIRA Service Desk.

4. Tools / Libraries Used
● Leiningen
● clj-http
● data.csv
● tools.cli
● logback
● vi / Fireplace
● data.json
● clj-time
● tools.edn
● tools.logging
● midje
● user.clj
JIRA REST API
https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis

5. Example Command Line
From sources:
lein run -m cosla.main open-per-day
From standalone uberjar:
java -jar <path/to/cosla.jar> open-per-day

6. Example Output (csv)

7. JIRA Ticket Concepts
● Statuses vs. Resolutions
● Workflows
● Transitions
● JQL
– Project = JRASERVER and Resolution is empty
order by Created
● REST API
– https://jira.atlassian.com/rest/api/2/search?jql=project=%27JRASERVE
R%27%20and%20resolution%20is%20empty%20order%20by%20%27create

8. JIRA Workflows!
Source: https://jira.atlassian.com/secure/attachment/67504/Workflow%20with%20labels.png

11. Code Example: JSON

12. Configuration (Excerpt)

13. Possible Enhancements
● OAuth Login
● Summary reports / graphs (maybe w/Incanter)
● Cache JSON data to disk
● Upgrade Clojure / libraries
● Less code?
● More reports!