Configure Jira Tempo plugin to send reminder without closure

[Stefano Ortelli]

Is it possible to configure jira tempo plugin to send a reminder for an incomplete timesheet without having a closure? The closure and timesheet approval are an overhead, we want just an automatic system to notify the developers, if they have forgotten to fill the timesheet of the last week.

[Susanne Götz [Tempo] · Accepted solution]

This sounds like a useful improvement. Please create an Improvement/ Feature Request in our Tempo Timesheets Project https://tempoplugin.jira.com/browse/TT and it will be evaluated by Tempo management. Other users can then comment and vote on it.

[Stefano Ortelli]

Hello Susanne

Thanks but we don't want to bother developers with a reminder email, if they have filled the timesheet of last week. It's really annoying receiving reminder for something that you have done because:

1. You have to switch context and go back to check if you have really forgotten something
2. After a few reminder people will ignore them and trash them directly

If I want a simple reminder email, I can also create cron job to send it, but as said it isn't really useful, it just bother the people and at the end they will ignore it and trash it. The "late reminder" is instead really useful, just the people, who hasn't filled the timesheet of the last week, receives it.

But I want to give you a clearer example, do you think it would be useful, if the seat belt alarm in the car would beeps one minute long every time the engine starts also if you fasten or have already fastened the seat belt?

To summarize it, the status reminder has no logic and it's useless, the late reminder has logic and it's useful.

[Susanne Götz [Tempo]]

Hi Stefano,

it is not possible to sent a late reminder without closing the period, but you can send the status reminder that is sent to all users.

The Tempo Scheduler is independent of the Approval Process.
It can be used to send a late reminder to users that have not logged the required hours for the period and then close it. This can be useful if you do not want users to change worklogs in the past.

Kind regards,

Susanne