• 6
    • 10
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      It would be beneficial to have the option to add to SLA reports the ability to use JQL and select a drop down on the report that goes back further than a year.

      Unable to render embedded object: File () not found.

          Form Name

            [JSDSERVER-2188] Allow for history on Service Desk reports to go back further than a year.

            We recommend companies to use JSM, but they can get a maximum of one year annual report in reporting. I think it's funny, it's pretty hard to explain that to my clients because it doesn't make sense.

            Gülçin Nacak added a comment - We recommend companies to use JSM, but they can get a maximum of one year annual report in reporting. I think it's funny, it's pretty hard to explain that to my clients because it doesn't make sense.

            The canned reports in JSM are great, but there's no way to render more than 12 months of the most recent data on the screen. I think if you just provided the JQL secret sauce, we could roll our own using issue searches. This is supposed to be an enterprise-class ITSM tool. Give us the ability to report on key metrics, using any time slice we want. Improving the built-in reports UI shouldn't be that difficult. Instead of the finite list of time slices (Past 48 hours, Past 7 days, Past 14 days, etc), add a calendar select option that lets us pick the from and to dates, and an interval slicer (by day, by week, by month, etc). This isn't a difficult feature request to develop.

            Rich Nacinovich added a comment - The canned reports in JSM are great, but there's no way to render more than 12 months of the most recent data on the screen. I think if you just provided the JQL secret sauce, we could roll our own using issue searches. This is supposed to be an enterprise-class ITSM tool. Give us the ability to report on key metrics, using any time slice we want. Improving the built-in reports UI shouldn't be that difficult. Instead of the finite list of time slices (Past 48 hours, Past 7 days, Past 14 days, etc), add a calendar select option that lets us pick the from and to dates, and an interval slicer (by day, by week, by month, etc). This isn't a difficult feature request to develop.

            @david Milligan: At this point I think Atlassian is going for a cloud-only approach. We'll probably never going to see additional features for DC I'm afraid, just bug fixes

            Tobias Schär added a comment - @david Milligan: At this point I think Atlassian is going for a cloud-only approach. We'll probably never going to see additional features for DC I'm afraid, just bug fixes

            Created: 06/08/2015

            Current status: Unresolved

            Current Date: 02/08/2022

            Current waiting Time: 2,553 days and counting....

             

            David Milligan added a comment - Created: 06/08/2015 Current status: Unresolved Current Date: 02/08/2022 Current waiting Time: 2,553 days and counting....  

            Tobias Schär added a comment - - edited

            Should be nothing more than a toggle - right? Best case scenario would cover the following:

            • Be able to specifiy a specific date range ("from" and "to" selection)
            • Select how it should be displayed for this period (days, weeks, months, quarters, years)

            If this cannot be implemented visually, please ensure that this data could at least be exported this way.

            Tobias Schär added a comment - - edited Should be nothing more than a toggle - right? Best case scenario would cover the following: Be able to specifiy a specific date range ("from" and "to" selection) Select how it should be displayed for this period (days, weeks, months, quarters, years) If this cannot be implemented visually, please ensure that this data could at least be exported this way.

            Can't wait to have this implemented.

            Konrad Kuźma added a comment - Can't wait to have this implemented.

            Not that Atlassian is going to listen to their customers but this shouldn't be that hard to figure out.  At a custom date range to your list and if the data is in the database how hard is it to lookup?

            Even support is recommending a plug-in which does work but the data is in CSV format and you need to really massage the data to make it work.

            Kyle Hughes added a comment - Not that Atlassian is going to listen to their customers but this shouldn't be that hard to figure out.  At a custom date range to your list and if the data is in the database how hard is it to lookup? Even support is recommending a plug-in which does work but the data is in CSV format and you need to really massage the data to make it work.

            I don't believe this. After looking for the resolution how to get a report of the last few years I see this isn't possible yet. Come one Atlassian!? Are you serious? How we can compare the years of the incoming Servicedesk requests if this option isn't available? Please make this possibile soon. Thanks in advance.

            Davy Janssen added a comment - I don't believe this. After looking for the resolution how to get a report of the last few years I see this isn't possible yet. Come one Atlassian!? Are you serious? How we can compare the years of the incoming Servicedesk requests if this option isn't available? Please make this possibile soon. Thanks in advance.

            MB added a comment -

            This feature would really help us to analyze the growth, change and efficiency of our service desk / support. One year is not enough to create useful reports which help us in analyzing specific situations.

            Is there a workaround for the meantime?

             

            MB added a comment - This feature would really help us to analyze the growth, change and efficiency of our service desk / support. One year is not enough to create useful reports which help us in analyzing specific situations. Is there a workaround for the meantime?  

            This would have to be one of my biggest issues with Jira. being able to go back 12 months is not helpful when you are trying to compare year on year issue growth.

             

            Trying to justify extra staff without being able to go "Well in 2016 we averaged 30 tickets raised a month, 2017 we averaged 90 tickets raised a month, 2018 we averaged 150 tickets a month, and so far in 2019 we've averaged over 400 tickets a month." to show the growth of your helpdesk. This functionality was available in our previous helpdesk software before upper management forced a migration over to Jira service desk because they were already using Jira for project management and had this idea that one system would be superior. Even though we've lost 80% of the functionality our old system had and the only recourse we have is to go on Atlassians forum, find a bunch of other system administrators complaining about the same issue, and vote on a Jira ticket that maybe one day will lead to the functionality that you think would be standard.

             

            And in the meantime deal with the current threadbare system for five years.

            Christopher Watson added a comment - This would have to be one of my biggest issues with Jira. being able to go back 12 months is not helpful when you are trying to compare year on year issue growth.   Trying to justify extra staff without being able to go "Well in 2016 we averaged 30 tickets raised a month, 2017 we averaged 90 tickets raised a month, 2018 we averaged 150 tickets a month, and so far in 2019 we've averaged over 400 tickets a month." to show the growth of your helpdesk. This functionality was available in our previous helpdesk software before upper management forced a migration over to Jira service desk because they were already using Jira for project management and had this idea that one system would be superior. Even though we've lost 80% of the functionality our old system had and the only recourse we have is to go on Atlassians forum, find a bunch of other system administrators complaining about the same issue, and vote on a Jira ticket that maybe one day will lead to the functionality that you think would be standard.   And in the meantime deal with the current threadbare system for five years.

              Unassigned Unassigned
              jcastro Jose Castro (Inactive)
              Votes:
              76 Vote for this issue
              Watchers:
              41 Start watching this issue

                Created:
                Updated: