Worklog calendar doesn't respect closed project when used in combination with tempo timesheet

[phalassek]

When using Worklog calendar to log time, it doesn't respect closed accounts when used in combination with tempo timesheet. when i use the normal logging function in jira, i'll get a note about the closed account, but not with worklog calendar.

[Volodymyr Krupach]

Hi Peter,

Currently I am rewriting major part of the Work Calendar to rely on JIRA REST API. Particularly time logging will go through REST method. If Tempo integrated warning or error into appropriate JIRA REST method or rather into "time reported" JIRA event then it will be shown during the reporting. I guess that the currently code that handles time reporting does not trigger appropriate JIRA event and that's the bug.

Sooner than a month from now I will release new version of the Work Calendar and will test it with Tempo for the case you described.

Thank you for reporting the problem! I will update you once it resolved.

[phalassek]

Thanks for the support. I'm looking forward to it.

[Volodymyr Krupach]

Hi Peter! Please update Work Calendar to the latest version that should allow reporting on non-editable issues if that's configured for your JIRA. Please see "Allow editing of Closed Issues": https://confluence.atlassian.com/display/JIRA/Allow+editing+of+Closed+Issues. Unforunatley "Allow logging on closed accounts" and "Allow logging on not editable issues" are Tempo's flag and JIRA is not aware of them. So Work Calendar ignores these Tempo settings.

[phalassek]

Hi Volodymyr, we really need this feature and are willing to pay to get it done. Can you please contact me about that? Thanks, Peter

[Volodymyr Krupach]

Hi Peter, I will investigate Tempo API to see if I can integrate with it. Another thing (if Tempo API gives what we need) I need to think is how to make your custom code "plug-able hook" so your still can update Work Calendar to never versions and have your custom code in place. Will update you tomorrow.

[Volodymyr Krupach]

Peter, replied via email.