We need the ability to specify dates back in time. While it's nice to have the predefined options for reports, there are times we need to know the data for specific time periods. The data should be there- it's just a matter of having reports being much more customizable than what's provided out of the box.

Reporting capabilities are critical to the proper functioning of a healthy service desk. Reporting generally needs to be bolstered to make it more clear on trends, post-problem analysis, and leveraging the investment of the Atlassian ecosystem.

Having just moved from Jira Cloud (where this capability is available) to Jira server (where it is not) we are now having to amend our internal processes to accommodate this lack of functionality. This needs to be resolved ASAP, if it works in Cloud it is possible

I think I have an idea about why Atlassian does not provide custom Start&End dates (yet).

It turns out JSD tries to include all non-complete issues in SLA reports. We realized this while developing "Service Desk Reporter" plugin. If an SLA timer is not complete yet but the goal time is already breached, then JSD will coutn the issue as a breach and will show on the last day of SLA report graph. I guess in order to preserve this behavior, Atlassian only gives date options that always includes the current moment but goes back n days to the past. As you may have realized, this "n days" means "n x 24 hrs" which results in a report start date that is in the middle of the day, n days before. Very frustrating. The report output is always unstable. You cannot get the same report twice.

Actually this is not a technical limitation but rather a design decision that Atlassian made. Our current implementation in "Service Desk Reporter" allows the user to use create date, update date, resolution date and SLA Stop Date for date filters and define custom start&end dates for whichever one you choose. Atlassian JSD report implementation always uses "SLA Stop Date" as referance date and without custom start&end dates. There does not seem to be any Technical reason why Atlassian coud not do this. If we could, so can they. After all it is all about selecting which issues to include in the report, the rest is the same.

Actually, filtering the issues based on SLA Stop Date was the hardest part of the implementation, which JSD already does. Other options are far easier. Just simple JQL.

By the way, we recently released a new version of Service Desk Reporter which includes bugfixes and optimizations as well as a REST API for integrations, aside from already present Excel export option.

We are also in need of custom filter.  One year make no sense now that servicedesk is available since a lot more then that.

The data also is in the database.

Given that your preconfigured dropdown list is only an abstraction that ultimately selects a START and END date for the SQL query, why not allows us to choose our own dates for reporting? Seems a bit silly that we even have to ask for this. But here goes....pretty please, oh great Withholder of Standard Features?

Our need is we want to see year over year reports so we can justify headcount and see trends

The lack of this feature is ruining an otherwise great reporting tool.

We send our customers SLA reports every month but we can only export 30 days worth of data. The ability to filter the reports by month or define custom date criteria is a needed feature.

I can't imagine this being too hard to put in place and I would have expected it to be a basic reporting feature.

Customer:

"I would happy this feature will be available also for the Jira Software".

This is another instance of functionality that seems pretty basic being completely missing. (The other is being able to replicate service desks.) How can a system that considers itself to be best-in-class be missing such basics? I'm not impressed.

Seriously how hard is this? This really needs to be implemented.

I have the same issue here: I need to create monthly reports, that cover a whole calender month.
I managed to filter the reported timeframe with "created >= startOfMonth(-1) AND created <= endOfMonth(-1)" (last month), but still have the issue, that the report shows the wrong timeframe. It still shows the "last 30 days" or "last quarter", but only the tickets that were created in the timeframe given by the JQL term (see screenshot).

Please allow the user to select the timeframe that is displayed on the X-axis of the graph.

I am just now realizing this is not a feature in JSD. Strange as this is a feature in every ticketing system I've ever used (including the free stuff) - Spiceworks, BMC Remedy Force, Kayako, Absolute Helpdesk, Zendesk, etc. Hope to see this in the product roadmap as many of our departments are more than willing to expense licenses for their own instance but it will be a non starter if they can't see richer reports to make data driven decisions.

Hi [Jacquesverryn]

Sorry for the misunderstanding. I just now understand that you are specially interested in graphs. My bad.

Hi Emre

Can you provide a screenshot where this is applied to the SLA Graph Reports?

Regards
Jacques

jacquesverryn
Service Desk Reporter plugin allows you to define start and end dates for your report, down to minute resolution.

I had another look. Does not look like the Service Desk Reporter plugin helps me with my issue.
The plugin gives a issue filter type result.

We require fine grain date range on these

Please JSD team, can you look into adding From, To and Interval = (Month, Week, Day) fields on these?!?!?

It is great that there is a workaround in the form of a plugin.
Problem is it is a licensed plugin with cost to fix something very basic.
Yes I can see the plugin does a lot of other cool things as well.

I'm just getting very concerned about the fact that JIRA Service Desk needs a lot op PAID work arounds to get it to work sensibly
JSD-218 is another example where we are now looking at buying JEHM to solve the issues mentioned in that issue.

@Atlassian, JIRA Service Desk is not cheap, and having to plugin licensed add-on upon add-on is not appreciated

Hello Everyone,

We saw that JSD reporting was limited, it was a real pain for a lot of people (including us) and Atlassian wasn't gonna fix it anytime soon. So we developed a custom report for JSD which gives you the ability to define custom datetime intervals, report on elapsed/remaining time and even export to excel. "Service Desk Reporter" is available on the marketplace today.

You can get it from: https://marketplace.atlassian.com/plugins/tr.com.obss.jira.plugin.service-desk-reporter

Have a good one...

This seems indicative of a larger problem with JIRA - all of their built in reports go off a "Days Previously" value, rather than a user entered date range. Is there a JIRA ticket for that issue as well? Starting a report from a random date based on whenever you happen to run it doesn't do anything useful.

Any progress on fixing this issue, or has this been abandoned? Please let us know so that those of us who depend on making these reports are not left hanging hopelessly. Please be honest with us since we have paid for this product. If you do not plan on fixing this anytime, we need to know so that we can move on and set proper expectations with our stakeholders and managers. Thank you.

Agree. There is absolutely no value in the reports if I can't set a specific date range. This must be implemented ASAP or we might be forced to change system all together to one that has god reporting. We can't give reliable SLA reports as it is now.

Still not planned? Not sure why it was not implemented in the first version, this is basic reporting 101, we need custom date range.

Please advise at your earliest convenience.

Thanks,

Being able to generate reports for specific timeframes is crucial to managing a service desk. Are there any plans to implement this feature?

Guys, this is killing us. Customers cannot get consistent reports as is.