Home Case Studies
Trunkrs is a logistics company that offers delivery services for businesses.
Trunkrs offers features such as real-time tracking, delivery notifications, and flexible delivery options.
Trunkrs teams gather products from web shops and sort them in the warehouse. Then, they deliver them to regions and finally to the end-consumers. The company also takes care of overall Customer Support. End customers can ask the Support team where a specific parcel currently is or report that it arrived damaged. Trunkrs provides webshops with dedicated agents to take care of logistics so that the web shops they work with can focus on selling products. The company mostly helps out middle-size web shops ensuring they can support their clients as comprehensively as large, well-known corporations. While Trunkrs’ main office is based in the Netherlands, it operates as a remote-first company with a global workforce that spans across different regions, mostly the Netherlands and the Philippines. The employees use different solutions from Atlassian, merged into one Cloud instance.
Each month, the Human Resources team in Trunkrs makes sure that all financial information provided by the employees is correct.
In order to pay the employees their salary at the end of the month, the HR team has a task plan with 25-26 steps to complete. They have a whole hierarchy structure with Epics, tasks, and subtasks in their Jira instance. This is why, Trunkrs company needed to arrange an efficient approval and double-check process. The employees estimate task resolution time. For example, a specific task can be estimated to take 2, 4, or 8 hours, based on the team’s definition. Depending on these estimations, the team members track tasks accordingly. As Epics are used to separate the tasks, the HR team couldn’t use them to build effective templates structure and optimize their work. For this reason, the employees started exploring how to use tasks and sub-tasks instead. This proved to be challenging, particularly whilst creating related issues and inheriting tasks in new documents.
Issue Templates for Jira reduce the time spent on creating issues and prevent the risk of errors and lack of information.
The Issue Templates for Jira plugin significantly speeds up issue creation. Instead of typing in almost the same data again and again, you can create flexible templates for repetitive tasks and their structures in no time. These templates can be customized to fit specific project requirements and allow teams to standardize issue creation across projects.
The representative of Trunkrs, Paul van Rijswijk, used the app for templating in the former company and decided to recommend it.
The previous organization Paul worked with was related to defense. For this reason, they were structure-organized and required extraordinary data security. Issue Templates for Jira turned out to be safe enough and significantly speeded up the work of the QA team. The plugin made it possible to create a template even for the complex release that 4 teams were working on. Before, creating tasks took 6-7 minutes per issue, and manual double-checking of the structure a day or a half. With Issue Templates for Jira, all Epics, stories, and sub-tasks along with necessary information were created in seconds and could be quickly verified and marked as done in Jira. The plugin helped avoid duplicating work in this team, so Paul thought it would do just as well in Trunkrs.
How does it work?
Save time and autofill your Jira issues
Variables allow you to input a value once and refer to it in multiple locations. You can also inherit field values from parent issues, such as components and versions. The plugin can calculate date fields based on the current time and automatically assign tasks to either the project lead or the user who created the issue.
Automate the creation of recurring Jira issues
Enhance the quality and efficiency of your work. The plugin allows you to duplicate Epics along with their stories and sub-tasks, as well as regenerate linked issues. Additionally, you can replicate customized hierarchies and implement templates for existing issues. These actions can be performed using a transition or automation features in Jira.
Issue Templates for Jira makes it possible to create an issue, describe it with all necessary information, and then use it automatically in sub-tasks, sub-issues, or stories.
The company mostly appreciates how the app works on complex issue structures in Jira. This is why Issue Templates for Jira comes in handy when the HR team does administrative tasks related to the salaries of the employees. Thanks to templating, instead of manually creating all tasks and sub-tasks, the team members just need to put the current year and month on their issues as all the structure appears automatically. Afterward, during double-checking with the CEO, consistent templates are more than helpful. It’s possible to see in Jira whether inherited subjet-related issues were already checked. It makes reporting easier and faster, even when it comes to dealing with a lot of data, which is the case in Trunkrs.
Get in touch
Head of Sales | Atlassian
Our consultant is at your disposal from 8 AM to 5 PM working days from Monday to Friday for any additional questions.