Click to View Jira Time‐In‐Status WIKI
Retrieve Jira Issues via Jira v3 REST API, and calculate amount of time issues have spent in any combination of defined Issues States. All user-defined states resolve to TO DO, IN PROGRESS, or DONE. A configuration file is created which maps issues statuses to 'Active' or 'Waiting', and is used to calculate total 'Active Days' and 'Calendar Days'.
It can be difficult to obtain this information from a Jira Cloud Instance, as it requires accessing all the change logs for an issue. This tool obtains all issue change logs (including where the number of change logs exceeds maximum changes logs per API request).
(Will update help files soon -- feel free to comment and ask questions)
Utility to determine amount of time a jira issue has spend in any status
Primary Purpose - retrieve ALL issueLogs for stories in order to find and analyze about of calendar time, and 'In Progress' time a Jira Issue has spent in any particular state.
- Retrieve Issue Status mapping from Jira to determine if any given issue status is a 'TO DO', 'IN PROGRESS', or 'DONE' -- this issue is written to a local file, but can be overriden
- Outputs to csv file with the following columns: key,type,created,featureTeam,summary,epicKey,parentIssueKey,currentStatus,labels,start,end,status,activeWork,calendarWork,totalBusinessDays,totalBusinessHours_8HourDay,transitionAfterHours,exclude,reason
- Will create a local config file that contains userName, jira api token, base jira url, default project code
- Supports extracting Json from any Jira issue
- Supports selecting issues for Time Analysis by entering list of issue keys, or by entering JQL, or by entering an Epic Key (will analyze all children of an Epic)
- Provides views/extracts of various Jira configurations, including list of status configurations for a project, list of issue types, etc
