About

This report shows you the state of your issues over time. Unlike the Issue Values Snapshots by Date Report, this report evaluates the state of your issues at all points in time over an entire report interval, rather than picking the issue state at a specific point in time. This allows you to quickly find and report on issues that had issue values for only a short period in time.

For example, if you run a report with a Time Period of Year to Date and select an Interval of Monthly, Dataplane will show you every value that your issues had for the selected Value Of field during the entire month of January, every value they had during the month of February, and so on, regardless of how long the issue had that value.

If an issue had multiple values for the field selected by the Value Of option during the reporting period, the report will include each of those values when breaking down the results. For example, if an issue had priorities of both High and Medium during a given time interval, the issue would be counted once for the High value and again for the Medium value.

In the Segment By option, you can select from two different variations of most fields: the current value of a field and the historical value of that field. The current value of a field represents the issue's field value at the time the report is run, whereas the historical value represents the value the field was set to during each date interval in the report. For example, if you use a JQL expression to select all issues that are currently closed, you could use Status (Historical) for the Segment By option to see how the statuses of those issues varied in the past.

The Statuses to Include option allows you to include only issues that had the specified statuses during each reporting interval. Although you can filter by status from the JQL search box as well, JQL filtering is always done based on the current state of the issue, rather than the issue's state on the reporting date. You can use this option to select issues that were open (or any other value you specify) during the reporting period, even if the current status of the issues may be closed.

See also the Issue Values Snapshots by Date Report.

Common Uses

Use the Issue Values by Date report to find transitional values in your issues. For example, when using JIRA as a help desk, you may want to know how many incidents occurred with High priority during a given week, regardless of how long the issue was in that state. An issue may start out with a priority of Medium, get escalated to High, and then get reduced in priority later, all in the same day. This report allows you to see how many issues ever reached High priority, even if an issue only had that priority for a few minutes.

In this example, we would set Interval to Weekly, select one or more projects or project categories, and select Priority for the Value Of option. You can add any number of additional segmentations to further break down the results.

If you instead ran the Issue Values Snapshots by Date Report, it would only show how many issues had a priority of High at the very start of each reporting interval, for instance at the beginning of each week. If the help desk works Monday to Friday and closes most issues before the weekend, you're better off running the Issue Values by Date report so as not to miss escalations made during the week.

Page Contents

Copyright © 2017 Arsenale Systems, Inc. · All rights reserved · Contact Us · Powered by Atlassian Confluence