The Script Series, Volume 3: How ScriptRunner and Structure for Jira scripts help you achieve more in Jira
We are excited to announce that we have teamed up with ALM Works to launch our first partnership on the Adaptavist Library.
We created the Adaptavist Library with a vision of creating a hub for ready-made scripts and resources. Part of this vision is to collaborate with our Partners to feature scripts for their apps on the Adaptavist Library and by doing so, we aim to deliver value for our mutual users by giving access to ready-made solutions to frequent challenges they face.
If you’re new around here, it’s time for a quick recap. Check out our other blog posts in The Script Series below to find out more:
Structure for Jira is an ALM Works app which helps you create and manage hierarchical lists, called structures. A structure has adaptable hierarchies and can contain Jira issues, folders and more. This means users can visualise, track and manage progress across Jira projects and teams with a familiar spreadsheet-like view of Jira issues. This collaboration focuses on utilising the power of ScriptRunner and Structure to automate, customise and extend your Jira.
To understand how these scripts work in practice, take a look at these use cases below:
Do you want to easily filter your issues in Structure?
JQL is the most powerful and flexible way for you to search for your issues. We have curated 3 JQL Query scripts for Structure to enhance your searching so you don’t have to spend time manually filtering issues or creating your own scripts.
I am in charge of a large project with multiple teams involved. The teams are all using different boards to keep track of their progress. This is making my Jira instance overrun with data and I’m finding it difficult to see the overall picture. Structure solves this problem for me as I can populate the data from all teams involved onto one structure board. To make sure my structure is kept up to date, the ‘Insert issues into a structure using a JQL query’ script adds all new issues created by the teams on their respective boards to my structure.
In this structure, I need to be able to filter my issues. For example, I need to know how many of the issues have a High Priority status and when were they created. I can use the ‘Add a JQL filter to a Structure’ script to filter these issues so I don’t have to manually search for them.
As my Structure board is full of data that spans from days to weeks, to months old, it’s important that resolved issues are not sitting in my structure. Therefore, I use the ‘Remove issues from a structure based on a JQL query’ to automatically review all issues with a status of ‘Done’ and remove them from my board.
Are you fed up of wasting time manually changing ownership of structures or generators?
A Project Manager is being replaced but they have multiple structures and generators. Instead of manually changing the ownership of these structures and generators to the new hire, I decided to automate the process by using the ‘Bulk change the owner of structures and generators’ script I found in the Adaptavist Library.
Are you looking for an easy way to administer your structures?
In my Jira instance, I have multiple structure boards and it can often get confusing. I use the ‘Show all structure boards and corresponding item counts’ script to get a quick overview of all my structure boards and the number of items that are included in each one. This means I can easily keep track of everything in one place.
It’s important for me to keep my structure boards organised and suited to my own requirements. The ‘Customise sorting manually or using an expression’ script helps with this as it gives me the flexibility I need to sort my boards either manually, or by using an expression to sort by assignee and key.
The ‘Show work logged per user and issue for a structure’ script has become essential for me. As part of my role, I need to quickly see what work has been done and who has done it. Previously, I found it very time consuming to manually find out this information, but now with this script I have more than halved the time it takes to get an overview like this.
Do you want the ability to extend your structures beyond the built-in capabilities?
As a Project Manager, I find using the ‘Extend a structure with all issues under an epic and include all linked issues’ to be incredibly useful, because I need to have visibility on all issues within an epic, as well as all linked issues to get the full picture. In addition, I need the ability to decide which linked issue types I want to be displayed for more granularity. This script is also beneficial to me as I can see the structure of an epic or linked issue.
Head over to ALM Works blog where Solutions Engineer, Phil Heijkoop gives his thoughts on the benefits of using ScriptRunner with Structure for Jira. We are excited to continue working with ALM Works over the coming months to add new Structure & ScriptRunner scripts to the Adaptavist Library.
At Adaptavist, we are always looking to improve and expand the usability of the Adaptavist Library, to give you the best experience possible. We hope that our new Partner Scripts will help you get more out of the Adaptavist Library.
Haven’t tried out the Adaptavist Library yet? Check it out