It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Understanding Tempo Scheduler

MarkW Mar 04, 2014

I just want to make sure I understand the Tempo period scheduler as we noticed it is not closing the period.

We have the Temppo Period Scheduler configured for a Type "Period", Repeat On "Monday", Make Scheduler Close "checked", Close "0" working days after end date, no email settings turned and the scheduler marked active.

Is there something that we are missing? Our expectation was that the February period would close automatically but it did not. We thought that using the scheduler would close the period no matter what the status of the timesheets were.

Does the Period and Repeat On options play an additional part on when the period will close or are those simply for email notifications.

2 answers

1 accepted

0 votes
Answer accepted

Hi Mark

The scheduler is only blocking the period for adding and editing worklogs for Tempo Team members.

Periods in Tempo are maintained manually as documented on this page.
https://tempoplugin.jira.com/wiki/display/TEMPO/Period+Management

Hope this answers your question

Sverrir Tynes
Tempo support

MarkW Mar 12, 2014

Thank you for the response Sverrir. I did read that part in your documentation:

When the Scheduler is used to schedule a closure, users are blocked to add and edit worklogs within an Open Period after the closing date. In order to be able to add and edit to those worklogs after the closing date, they will have to ask the user with the Approve Timesheet permission for their team to give a short Grace Period to reopen the access. An overview of a Scheduler configured for a weekly closure can be seen in the screenshot below.

I retested that in our testing environment and it does block me from entering time. In our organization, we do not want to allow an grace period, which those with the approve timesheet permission can grant. I don't see there is a way to restrict that, if so then the scheduler would work..without we would prefer the period to hard close.

I think I will submit an enhancement for that if possible.

0 votes
MarkW Mar 12, 2014

Thank you for the response Sverrir. I did read that part in your documentation:

When the Scheduler is used to schedule a closure, users are blocked to add and edit worklogs within an Open Period after the closing date. In order to be able to add and edit to those worklogs after the closing date, they will have to ask the user with the Approve Timesheet permission for their team to give a short Grace Period to reopen the access. An overview of a Scheduler configured for a weekly closure can be seen in the screenshot below.

I retested that in our testing environment and it does block me from entering time. In our organization, we do not want to allow an grace period, which those with the approve timesheet permission can grant. I don't see there is a way to restrict that, if so then the scheduler would work..without we would prefer the period to hard close.

I think I will submit an enhancement for that if possible.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Posted in Marketplace Apps & Integrations

Demo Den Ep. 4: Continuous Integration with CircleCI & Jira Software

Get ready! Demo Den Episode 4 is coming your way on Tuesday, May 28, 2018 with a Continuous Integration and Delivery special demo. CircleCI Director of Solutions Engineering, Eddie Webb will show us ...

486 views 0 4
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you