Timesheet report and Pivot report not visible after upgrade to JIRA 7

Issue #950 resolved
Jason Boyd created an issue

Hello,

We have lost the ability to run the Timesheet and pivot reports as we can't find them in the interface for our JIRA server implementation. Following the instructions in the wiki (http://www.jiratimesheet.com/wiki/Overview.html) we expected to find the reports per usual, but they are not present. Please see the attachment.

Thanks!

Comments (8)

  1. Jason Boyd Account Deactivated reporter

    I have found the root cause, and am not sure you are able to help or not. We have JIRA Service Desk which is resetting the direction of the report page. The typical URL is: http://ease.labanswer.com/projects/<project code>?selectedItem=com.atlassian.jira.jira-projects-plugin:report-page, but with service desk, it becomes http://ease.labanswer.com/projects/<project code>/reports/workload.

    Not sure where to go from here, but I think this data will be helpful for you.

  2. Andriy Zhdanov

    Hi Jason,

    Could you please check if you have Timesheet Reports and Gadgets plugin installed in Administration - Add-ons - Manage add-ons?

    Thank you.

  3. Andriy Zhdanov

    Well, if you cannot access project reports page as you have found, i.e. with http://ease.labanswer.com/projects/<project code>?selectedItem=com.atlassian.jira.jira-projects-plugin:report-page, then you may try to open plugin reports directly using: http://ease.labanswer.com/jira/secure/ConfigureReport.jspa?reportKey=jira-timesheet-plugin:report for Time Sheet Report or http://ease.labanswer.com/jira/secure/ConfigureReport.jspa?reportKey=jira-timesheet-plugin:projectpivot for Project Pivot Report

    Alternatively, you may add Timesheet or Project Summary gadget to dashboard, and access reports from there.

    I may leave this issue open to add quick link similarly to Tempo Timesheets, otherwise I'm not sure what else I can do.

  4. Jason Boyd Account Deactivated reporter

    Thanks @azhdanov, I'll try the dashboard plugin route. I've also opened up a ticket with Atlassian as I think this root cause is with them, not with your plugin.

  5. Log in to comment