1. Tempo Avatar Tempo
  2. Prime
  3. cloudtimesheet
  4. Issues

Timesheet Issue - Not displaying correct nor recent hours per month

Issue #985 resolved
Alex Zoric created an issue

Capture1.PNG

As shown in the screenshot above. The date range is from 1st of January 2017 to current (12 Sep 2017). The issue lies in no hours being displayed for the last 3-4 months and the hours that do display from January to May are incorrect as we put in a lot more hours than shown here.

Below is my selection criteria. Now this may be something I am doing wrong, not really sure. Keep in mind we have no other add-ons active other than JIRA toolkit plugin and this.

Capture2.PNG

Configuration: Capture3.PNG

Capture4.PNG

Any suggestion appreciated.

Thank you.

Comments (14)

  4. Alex Zoric Account Deactivated reporter

    Hi Andriy,

    No. We use ‘smart logging’ I believe it is called e.g. in our commit messages we would have syntax as such – JR-456 #time 1h 30m commit message here - and this would log the specified time in the work log in JIRA. I believe Tempo is an add-on, right? Which we do not use whatsoever.
    There was an update on all our Atlassian accounts recently e.g. JIRA, BitBucket & Confluence. But it just seems like an UI update. I have not reviewed the changelog.

    What I can do tomorrow is test it on a different machine and a different user account and see if the issue persists.
    I’d let you know more tomorrow then. Because it could be something on my end which I cannot see right now.
    But at the same time, I am not sure what it could be…

  5. Andriy Zhdanov

    It may be that issue relies in user names.

    It would be better to reduce time period, and narrow it to some user/issue and see if expected hours are in JIRA issue worklog tab but not in the report.

    Then you can collect support data to let me reproduce it locally. Enable Track Support Data option in add-on configuration, then reload report and click Download Support Zip button, and send it to me by email to support@jiratimesheet.com.

  6. Alex Zoric Account Deactivated reporter

    Sent you an email with the file attached. I'll further test the date range etc. first thing tomorrow morning.

  7. Alex Zoric Account Deactivated reporter

    Hi Andriy, quick update: I manage to get it working. The issue was with the 'filter or project' parameter. I have added 'all projects' there previously when the issue was happening but if i leave it blank, it seems to work and select all projects anyhow. Thanks for the help buddy.

  8. Andriy Zhdanov

    Hi Alex,

    Great! Am I right thinking All Projects is your filter that caused the problem?

    Thank you.

  10. Alex Zoric Account Deactivated reporter

    Yes that is correct. Leaving it blank seems to select all project anyhow though.

  11. Andriy Zhdanov

    Yes, this is expected behaviour. Though if you'd like to make it work with filter too, please let me know.

  12. Alex Zoric Account Deactivated reporter

    I tried selecting a one specific project via this filter and it retrieves correct data. It just seems that the 'All Projects' value in the parameter is causing the issue. All I need to be able to do is select a specific project or all projects and group it by another column; and this works. So no nee for any fix at the moment. Appreciate all the help.

  15. Log in to comment
Assignee
Type
bug
Priority
major
Status
resolved
Component
–
Version
JIRA Cloud
Votes
0
Watchers
2