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

Worklogs missing

Issue #487 resolved
Former user created an issue

Timesheet is missing worklogs entered today, is there any "waiting time" needed to show data?

Report URL: http://[Domain]/secure/ConfigureReport.jspa?startDate=17%2FFeb%2F14&endDate=2%2FMar%2F14&targetUser=ckraemer&targetGroup=&priority=&projectid=&filterid=16103&projectRoleId=&weekends=true&showDetails=true&sumSubTasks=true&groupByField=&moreFields=&selectedProjectId=11702&reportKey=jira-timesheet-plugin%3Areport&Next=Next

Please see screenshots for more details, thanks!

Regards, Hans-Hermann

Comments (16)

  2. Former user Account Deleted

    Hi Andriy,

    i´ll add the logging parameter during the next downtime, so at end of the week we should have more information. Keep you informed!

    Thanks & regards, Hans-Hermann

  5. Former user Account Deleted

    Hi Andriy,

    downtime was rescheduled to this friday, i´ll update this issue as soon as i have some content for you.

    Sorry for the delay!

    Best regards, Hans-Hermann

  6. Andriy Zhdanov

    Hi Hans,

    Meanwhile, could you please clarify in what browser do you see this issue? And is it the same in other browsers?

    Thank you.

  9. Andriy Zhdanov

    Hi Hans,

    I can see the following in log.1:

    Issue LOI-555 did not match filter, skipping.

    However I can't understand why, because on screen shot I can see that it does match the filter.

    Even though the following can hardly be the cause, let me check, what plugin version do you have? Because there was problematic behavior, fixed in 2.7.7, see Issue#483 (or #489).

    Or may be you have configured issue linking in Administration - Add-Ons - Timesheet Configuration, with Parent Issue Link or Parent Issue Field?

    Anyway, even if you would have this, log would mention parent issue, but not LOI-555 itself. So I don't think this is the case.

    Thus, I have just added more logging details about filter used, would you be able to install it from downloads? See jira-timesheet-plugin-2.7.9.jar. Note, it is latest 2.7.9 version just with some additional logging.

    Thank you.

  10. Former user Account Deleted

    Hi Andriy, we´re using v. 2.7.8.1, update was done on 21.03. Checking the configuration no issue linking is enabled, but this function is a bit confusing: In case of enabled, does it overide all report settings or is this just an addition of hours to specific issues? Just updated to v. 2.7.9, will have some checks today and send you new logs afterwards...

    Thanks & Regards, Hans-Hermann

  11. Andriy Zhdanov

    Hi Hans,

    Ok, great.

    Regarding issue linking, it's extension for Sum SubTasks, so if you organize your issues with links, it will make Sum SubTasks option take this into account.

    Thank you.

  12. Former user Account Deleted

    Hmm, can i also add the logging only temporary as described here?

    Already removed entries from log4j.properties and a reboot was already done. Next downtime is end of this week, but needed twice to lower log size...

    Entered:

    • log4j.logger.com.fdu.jira.plugin = debug

    • log4j.logger.jira.plugin = debug

    but cannot enter both values which should be set to "false"...

    Regards; Hans-Hermann

  13. Andriy Zhdanov

    Hi Hans,

    Oh, yes, temporary logging should do the trick, it may be even better. Turn on logging, perform actions, retrieve logs immediately. It will be easier to analyze them.

    I did not know about this way. Thank you for letting me know.

  14. Former user Account Deleted

    Hi Andriy,

    two things: 1. Logging via temporary doesn´t seem to work, cannot find any string "timesheet" with above mentioned settings 2. Checking the initial use query suprised me as right now it´s working. I created a new filter with the same parameters (sprint & assignee), the mentioned "LOI-555" was also included in the filter result. In the gadget report i could see the worked hours, so right now i cannot reproduce any wrong behavior.

    Just letting you know...

    Regards, Hans-Hermann

  15. Andriy Zhdanov

    Hi Hans,

    The second is great news! It should work. May be there were some changes in filter. Or may be filter results were cached some how. I'm closing it, if it happens again please feel free to reopen.

    Regarding temporary logging, it seems to work for me, I did not see anything logged just for 'com.fdu.jira.plugin', but got messages when I added 'jira.plugin'. So may be confusion is that it must be without 'log4j.logger'.

    Thank you.

  16. Former user Account Deleted

    Hey, yes, please close this ticket as it´s working.

    Regarding logging i´ll change settings as mentioned by you, perhaps you should do some more tests and update your FAQ section.

    Many thanks, Hans-Hermann

  17. Log in to comment
Assignee
Type
bug
Priority
critical
Status
resolved
Component
–
Version
2.7
Votes
0
Watchers
1