Problems after update Jira TimeSheet plugin from 2.3.7 to 2.3.16
gadget TimeSheet displays "There are no time tracking records for the period." when field "User" is empty
for 2.3.7 gadget displays efforts of logged user
and similar problem: gadgets 2.3.7 displays efforts for all projects if filter is emply. After update gadget displays "There are no time tracking records for the period." - we had to indicate project in settings
(as result we returned back to plugin v2.3.7)
Comments (12)
-
-
reporter -
Yes, with 2.3.16 there is a workaround/solution: add the following property to your jira/home/jira-config.properties and restart jira:
jira.timesheet.plugin.preserveWorklogAuthorCase=true
Note, it's not 100% solution, you might want to read through
#347, but the flag makes 2.3.7 behavior.Please let me know if it helps.
Thank you.
-
reporter yes, seems it's duplicate of
#347I hope it will help
jira/home/jira-config.properties jira.timesheet.plugin.preserveWorklogAuthorCase=true
Thanks
I'll try tomorrow
-
reporter - attached jira-config.properties.txt
jira v5.1.4 I've updated jira timesheet plugin to 2.3.16 again I've put attached jira-config.properties in jira home folder and restarted jira
result: nothing about jira-config.properties and jira.timesheet.plugin.preserveWorklogAuthorCase in jira logs
timesheet gadget works the same way as before: - nothing for users - ok for group but only if project selected
-
-
assigned issue to
-
assigned issue to
-
reporter I'm terribly sorry I've just seen .txt file extension here in
#355:( -
Hi Alex,
Ok, does it work without .txt extension?
If not, do you have project specified as well? I think you may be facing other or both problems, please check issue
#353also. See also http://www.jiratimesheet.com/#/wiki/Tips%20and%20Tricks - "Timesheet for project users", this may explain your case. -
reporter I'll be able to check tomorrow
-
reporter It's ok now thanks
-
- changed status to duplicate
Duplicate of
#347. -
- removed version
Removing version: 2.3.15 (automated comment)
- Log in to comment
Issue
#347duplicate?