![]() ![]() Our aim is to accomplish the following goals: Now let’s examine how the raw work log data from Jira can be processed in a spreadsheet to create visibility through tables and charts. You will need to set the following values: We will configure our script with a `.env` file. See the Jira documentation to learn more about creating an API token or get started and create one. Load environment variables from local file.īefore you can interact with the Jira REST API, you need to create an API token for your user.Wrap the Jira API to simplify REST calls.Additionally we will use the following npm packages to help simplify the process To access the REST API we will use a JavaScript application built with a Node runtime. Analyze the data with formulas and charts.Parse the JSON response to CSV and copy to the clipboard. ![]() Fetch Jira issues (with work logs) for a specific sprint through the REST API.The Jira REST API will provide us with issue and work log data in JSON format. Jira may not offer built-in reporting for aggregate user time logs, but the Jira REST API contains all the information we need to construct those data. Jira offers a few reports related to work logs and time tracking, but nothing that tracks a single user across multiple issues. Understanding a specific team member’s time across multiple issues, such as at the sprint level, is even more difficult. However, it is difficult to understand the time spent by each team member, since multiple team members can log time on the same issue. This provides a clear view into the aggregate time and progress on an issue and the granular log of the time entered. ![]()
0 Comments
Leave a Reply. |