Automating Tempo Planner with ScriptRunner: Fast, convenient, efficient
Tempo Team
Automation in Tempo is easy with the help of a tool like ScriptRunner! So far, most of the scripts published in the library will work with any of the three Tempo products (Timesheets, Planner, Budgets), but there is one that is exclusive to Tempo Planner.
If Tempo Planner is a mystery to you, we’re about to change that right now!
Tempo Planner is a resource allocation app for Jira that lets you quickly find available team members and maximize your resource utilization. With it, you’ll be able to boost the efficiency of your teams and simplify your planning process.
Today we’ll go over some use cases and scenarios for this ScriptRunner’s Tempo Planner script.
Today’s example: Get Tempo Plans Using the REST API for a Set Time Period
This script uses Tempo Planner, a tool to streamline the management of teams and resources to quickly find available team members and maximize your resource utilization.
As the name of the script suggests, ScriptRunner now has a way to remove some pesky manual labor and automate the process of pulling Tempo plans of interest for a given Jira Issue.
Where does this script shine?
Let’s take the case of Taylor, a team lead for Rougetech. Every month, Taylor and her team get together for their monthly planning. In it, they plan time for each team member on the tasks that they must do.
In other words, her current steps to see the total plans for the next 4 weeks are as follows:
In Jira, navigate to Tempo Planner and plan the task for the team
In your Tempo Planner page, you will have the possibility of filtering the view to your team. The capacity of the team and the individual members will be displayed for the determined period.
After the planning has been completed, Taylor will be able to revisit an issue to see who all the collaborators are, and quickly calculate the total time planned to see if it matches her initial prediction and budget.
The issue “Have Fun!” showcases all the planned time under “Collaborators”.
That being said, this is slightly tedious for Taylor because of the following:
She has to manually sum the time to find out how much time has been planned on the issue
It does not say when that time is being planned for as the issue shows the total planned time only
On the surface, this might not seem like much and it could end up simply saving 5-20 minutes per issue. But, lets not forget the following:
Taylor has to look at more than one issue every month, making her waste even more time
Taylor has to do the same steps over and over again when they can be automated
Taylor has no idea if all the planned time is evenly split or if it’s all planned during a certain week
This repetition of a mundane task could also be a widespread practice throughout the whole organization. Other team leads could be following the same practice (especially if it is standardized), meaning that the company is losing hundreds, if not thousands of dollars on such a little thing.
In other words, the script does the following:
Reduces the amount of manual labor necessary to attain the end result
Gets the total time for the relevant period immediately when visiting an issue
Decreases the potential human error to near zero
Automatically displays the planned time of a determined time period for an issue as a Jira custom field. This allows for reporting on planned time in the Jira issue view and to include the planned time information in other Jira reports
Compare total estimated time with remaining planned time. Enables you to quickly query on those issues that are over- or under-allocated
But the use case does not limit itself to monthly planning!
There are many other scenarios where this script can save precious time for the end user and the organization.
For example, a manager in a consulting firm could be looking at the staff's planned hours for a client’s issue to ensure that for a given time period, the time planned does not exceed the contractual agreement with the client. If it does, then the firm can let the client know that they will charge extra.
Or if for example people were logging time on an off-site issue (such as meeting clients or being on the road), then it would help a manager quickly understand how much time his team is spending off-premise, and help determine the remaining capacity of his team for a predetermined time frame.
How do I get my hands on the script?
The beauty in this partnership is its simplicity.
All you have to do is to copy-paste the script in your ScriptRunner terminal and tweak the variables to your use case.
Are there other scripts like this?
Today, we quickly went over one of the newly published scripts made by the Tempo-Adaptavist partnership for Tempo Planner and some scenarios in which time could be saved through automation.
More scripts have been published in the Tempo-Adaptavist library.
Sign up for a demo
Register
