This module contains code to access Jira, parsing both the JSON API via github.com/andygrunwald/go-jira in jirarest and code to parse a Jira XML file in jiraxml.
Various aggregate staticstics and reports are calculated/generated.
- Programmatically construct JQL
- Generate Markdown Reports from JQLs for addition to git repos or Confluence
Accessing a list of issues by JQL is avialable via the UI and API:
- UI:
https://{jira_host}/issues/?jql= - API:
https://{jira_host}/rest/api/2/search?jql=
The API auth can be provided by Basic Auth using an personsal API Token.
- Docs: https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/
- Token Page: https://id.atlassian.com/manage-profile/security/api-tokens
This module supports custom hoursPerDay and daysPerWeek settings per Jira.
This is described here and set in the UI via the screenshot below,
Also of note is that the hours per day can be set to a decimal value, such as 8.5, but the UI may not show it:
General discussion including using Jira XML to:
- export comments and issue link types
- create CSV for flexible reporting and import
Working Hours Per Day and Working Days Per Week are global values and cannot be set on a per-project basis.
| Goal | Example |
|---|---|
| Query by key | key = ABC-123 |
| Query by parent | parent = ABC-123 |
| Query by linked issue | issue in linkedIssues (ABC-123) |
| Query by reporter | reporter = "foo@bar.com" |
Downloading the project backlog view appears to be challenging. Here is some info on attempts to do this.
- What is the equivalent JQL query for a scrum board backlog
- How can I export the Backlog to csv or Excel or TXT?
Roughly:
project = <project_name> AND resolution = Unresolved AND status!=Closed AND (Sprint not in openSprints() OR Sprint is EMPTY) AND type not in (Epic, Sub-Task) ORDER BY Rank ASC
Stage is a common way to understand the stages of development given that many companies can use different statuses and workflows.
Stage the following stages (from Asana) and will provide a grouping capability for implementation-specific workflows into these standard meta statuses for consistent and canonical understanding of the process.
Not all the stages need to be used, however, the stages that are used can be understood in a canonical way.
An alternate, but related agile methodology is avialable from eSparkBiz:
As well as from BISS:
This is described as "The 5 Stages of the Agile Software Development Lifecycle" by Mendix.



