Andrei Cuzuioc
19th September, 2024
5 workarounds that make Jira Cloud taste more like Jira Data Center
You know when you go abroad and things that are familiar just taste a little different? Your favourite soft drink, or the fries at your favourite fast food chain?
Switching from Jira Data Center to Jira Cloud can feel like that at times.
Your favourite apps work differently because the platforms they're built on work differently, and there are things you like about both, they're just…different. When it comes to certain ScriptRunner features, for instance, the APIs that the apps are built on don't always allow for a perfect match on user experience or functionality, but does that mean you can't do what you need?
Heck no!
ScriptRunner for Jira Cloud doesn't have the exact same feature set as it does on Data Center, but here are a handful of workarounds in Jira Cloud for Data Center functionality to help illustrate that – just because it has to be done differently – doesn't mean it can't be done!
Cloud features
Get a detailed breakdown of current Cloud feature availability, and how to replicate Data Center functionality on Cloud, in our documentation.
1. Trim down excessive issue links to streamline your project backlog
Maintaining a refined project backlog is essential for operational efficiency and clarity. This ScriptRunner script enables the automatic trimming of issue links for any issue that goes beyond a specified threshold. This keeps your issues focused and manageable.
By prioritising the removal of the oldest links, it keeps your project's connections current and uncluttered. Using the ‘numberOfLinks’ JQL keyword within the Enhanced Search feature, your project managers can effortlessly keep their backlog streamlined.
2. Manage comment volume for a cleaner backlog
Following the theme of optimising project backlogs, another valuable solution involves managing comments on issues.
For issues overwhelmed by extensive discussions, you can help your teams by automatically reducing the number of comments on issues. You decide how many comments are too many comments, and the script will remove the oldest comments over this threshold, keeping discussions relevant and your backlog clear.
3. Automate issue cloning to create recurring tasks across different sprints
Want to save time and get consistency in your task tracking? Automate the cloning of issues and field data to facilitate recurring tasks across different sprints, and help your teams work more efficiently.
4. Change filter and dashboard ownership for a seamless transition
Getting stuck when a team member who created widely-used dashboards and filters departs? With the script below you can reassign ownership to another team member in a few keystrokes, ensuring no disruption to important business processes.
5. Archive issues that have not been updated for a specified period of time
By using a JQL search to identify issues that haven't been updated in the past 30 days, you can automatically archive these stale issues. With the script below, you can declutter the workspace, ensuring that active work remains in the spotlight and enhancing overall project management efficiency.
So there you have it. Some examples of workarounds that might be easy to miss, but which act like the *chef kiss* seasoning that you needed to make ScriptRunner for Jira Cloud taste like what you were craving! There are even more examples in our documentation, each with a link to the ready-made script to help you achieve your goals in Cloud!