Jira App Migration:  Top 10 Apps Evaluated

Highway Three awarded Atlassian Rising Star 2020

Which Atlassian plan is right for you? Take the quiz and find out


<p>Many of our Canadian clients have been asking about Canadian data residency for the Atlassian cloud products and we know how important that is to keeping your data secure when considering cloud products and SaaS. These concerns are especially true for those clients currently hosting their own on-premise Jira and Confluence; when you are used to keeping your data under your own control it can be difficult to transition to a cloud offering that will be storing your data in a foreign country.</p>



<p>Throughout 2021 Atlassian’s roadmap indicated Canadian data residency would be available late in 2021 or early 2022. <strong>We got bad news near the end of 2021 when Atlassian announced they would be delaying the launch date of data residency support for several countries, Canada among them, until 2023.</strong><a href="https://www.atlassian.com/roadmap/cloud?&amp;search=data%20residency"></a></p>



<div class="wp-block-image is-style-default"><figure class="aligncenter size-full"><img loading="lazy" width="716" height="268" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2022/01/atlassian-cloud-roadmap-canadian-data-residency.png" alt="Screen grab of the Atlassian Cloud Product Roadmap info for data residency in Canada" class="wp-image-1351" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2022/01/atlassian-cloud-roadmap-canadian-data-residency.png 716w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2022/01/atlassian-cloud-roadmap-canadian-data-residency-300x112.png 300w" sizes="(max-width: 716px) 100vw, 716px" /></figure></div>



<p><a href="https://community.atlassian.com/t5/Atlassian-Cloud-Migration/Data-Residency-Roadmap-Update/ba-p/1868602" data-type="URL" data-id="https://community.atlassian.com/t5/Atlassian-Cloud-Migration/Data-Residency-Roadmap-Update/ba-p/1868602" target="_blank" rel="noreferrer noopener">Atlassian had this to say</a> on the rationale for the delay:</p>



<blockquote class="wp-block-quote is-style-h3-blockquote"><p>Atlassian is committed to becoming a leader in data residency, and in order to provide you with the best solution and to support the number of locations we aim to support, we need to invest some additional time improving our data residency infrastructure. These investments will allow us to launch new locations much more quickly in the future and give us the ability to respond faster to new or changing regulations across various countries</p><p>We’ve made the decision to focus on improving our data residency infrastructure, which will allow us to launch new locations much more quickly in the future and give us the ability to respond faster to new or changing regulations across various countries. This work will also help accelerate other priorities that bring greater value to you.&nbsp;</p></blockquote>



<p>As long time software developers, we understand when feature requests collide with architecture in such a way that you must go backwards in order to go forwards, re-tooling your architecture in order to support growth. This reminds us of the analogy that compares building software with building a house… and after the house is built you want to install a pool on the roof. You likely didn’t plan for that in the design for the house, so adding that fancy pool is going to mean shoring up the foundation and supporting walls. In terms of adding support for data residency in several countries, Atlassian is now upgrading the foundation before adding the pool on the roof.</p>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>We respect Atlassian for being transparent and sharing with us their reasons for delaying. And we appreciate the time they are taking to make sure they get it right &#8211; while we want Canadian data residency, we don’t want it at the expense of security, stability and reliability!</p>



<p>For some good news: Atlassian has expanded the option to select data residency to all customers with a paid plan &#8211; previously this was available only to the Premium and Enterprise tier. We applaud extending this to a wider range of customers given the importance of data residency to so many organizations.</p>
</div>



<div class="wp-block-column" style="flex-basis:33.33%">
<figure class="wp-block-image size-full"><img loading="lazy" width="500" height="500" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2022/01/canadian-data-residency.png" alt="laptop with cloud computing image and Canadian flag" class="wp-image-1349" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2022/01/canadian-data-residency.png 500w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2022/01/canadian-data-residency-300x300.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2022/01/canadian-data-residency-150x150.png 150w" sizes="(max-width: 500px) 100vw, 500px" /></figure>
</div>
</div>



<p>Stay tuned and bookmark this blog post as Highway Three Solutions will keep this page updated with the latest information on when Atlassian will make available data residency support for Canada.</p>



<p><em>Are you unsure whether data residency is a requirement for you? </em>Government rules are always changing and part of our expertise is to understand how those regulations affect your adoption of the Atlassian cloud products.</p>



<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link">Contact us to find out if data residency should concern you</a></div>
</div>


Status of Atlassian Canadian Data Residency


<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/webinars?id=5-things-jira-cloud-migration" target="_blank" rel="noreferrer noopener">Watch the webinar</a></div>
</div>



<p>As we approach the sunset date for the Atlassian server products, the pressure to move forward with your migration can be stressful. From our previous migration webinars, we also know that many of you find the plethora of options and decisions bewildering at times. Added to this is the pace of changes: Atlassian is continuously improving their migration tooling and support.</p>



<p><br>If all of the above sounds familiar, join us for our next webinar to learn the fundamentals of migrating in the real world &#8211; the language, the tools, and the choices. We will bring you up to speed on the latest from Atlassian and share our tips on migrating in the real world.</p>



<figure class="wp-block-image size-large"><img loading="lazy" width="1024" height="576" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/11/Webinar-7-LinkedIn-Event-Banner-1920-x-1080-px-3-1024x576.png" alt="" class="wp-image-1231" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/11/Webinar-7-LinkedIn-Event-Banner-1920-x-1080-px-3-1024x576.png 1024w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/11/Webinar-7-LinkedIn-Event-Banner-1920-x-1080-px-3-300x169.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/11/Webinar-7-LinkedIn-Event-Banner-1920-x-1080-px-3-768x432.png 768w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/11/Webinar-7-LinkedIn-Event-Banner-1920-x-1080-px-3-1536x864.png 1536w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/11/Webinar-7-LinkedIn-Event-Banner-1920-x-1080-px-3.png 1920w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<p>On December 15th, 2021 at 02:30 PM Pacific Standard Time Join us for our next webinar and have lunch on us!</p>



<p>We know that your time is valuable, so as an incentive we are offering the first 20 people to register and attend the webinar a meal delivery voucher to be used at the restaurant of your choice. Don&#8217;t miss this great opportunity to learn more about Jira Cloud Migration.</p>



<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/webinars?id=5-things-jira-cloud-migration" target="_blank" rel="noreferrer noopener">Watch the webinar</a></div>
</div>


5 Things You Need to Know About Jira Cloud Migration


<p>What do you do when&nbsp;the&nbsp;rockstar&nbsp;server&nbsp;admin&nbsp;on&nbsp;your team&nbsp;accepts&nbsp;a promotion in a different division? That one person who managed the&nbsp;server like it was their baby: knowing&nbsp;when it was acting up,&nbsp;which addons it can handle — and which it can’t — and&nbsp;what needed to be done to coax it back online&nbsp;when the server&nbsp;went down. Again.&nbsp;For a local public&nbsp;sector team, the answer was to&nbsp;sunset their&nbsp;on-prem&nbsp;and switch to&nbsp;a&nbsp;solution in the cloud.&nbsp;&nbsp;</p>



<p>In early 2021, the&nbsp;DataBC&nbsp;team&nbsp;shared a request for a local provider to migrate their existing&nbsp;on-premise&nbsp;Jira server to the Atlassian Cloud. They wanted a solution that would mitigate the effort required to perform manual inbox triaging,&nbsp;with the ability to easily receive, track, manage, and resolve requests from their clients: other public servants as well as the&nbsp;general public.&nbsp;Following a formal proposal process,&nbsp;DataBC&nbsp;awarded the project to Highway Three Solutions&nbsp;due to the response package they created: it&nbsp;met the&nbsp;required&nbsp;deliverables, within the requested timeline, from a team with the experience and knowledge required to make the transition as smooth as possible.&nbsp;&nbsp;</p>



<h3>Processes for Perfection&nbsp;</h3>



<p>To ensure&nbsp;the&nbsp;cloud migration process&nbsp;was&nbsp;completed&nbsp;effectively and&nbsp;efficiently, Highway Three followed&nbsp;a defined process:&nbsp;</p>



<p><strong>Assessment</strong>&nbsp;– For this project, the client had determined the cloud was the right tool for them, so Highway Three&nbsp;helped them choose the right plan for their office,&nbsp;with a strategy to navigate the cloud-based authentication mechanism and&nbsp;security&nbsp;management.&nbsp;&nbsp;</p>



<p><strong>Planning</strong>&nbsp;– Highway Three developed a&nbsp;multi-phase&nbsp;migration&nbsp;plan to minimize the impact on the various teams involved, factoring in the time required for each task, assigning a professional to oversee it, and documenting the process from start to finish.&nbsp;&nbsp;&nbsp;</p>



<p><strong>Preparation</strong>&nbsp;–&nbsp;The team&nbsp;looked at the various plugins and configurations required to ensure the&nbsp;client’s teams could access the tools they needed following the migration.&nbsp;&nbsp;</p>



<p><strong>Testing</strong>&nbsp;–&nbsp;Prior to&nbsp;migration,&nbsp;H3&nbsp;extensively tested&nbsp;the&nbsp;DataBC&nbsp;system&nbsp;to ensure&nbsp;an essentially trouble-free experience for&nbsp;the end-users.&nbsp;Several test migrations helped identify concerns before they became problems.&nbsp;</p>



<p><strong>Migration</strong>&nbsp;– This is where the magic happens,&nbsp;moving the on-prem server data and associated attachments and projects to the cloud safely and&nbsp;comprehensively.&nbsp;</p>



<p><strong>Go-Live Launch</strong>&nbsp;– Once the system&nbsp;was&nbsp;configured and tested to ensure it&nbsp;was&nbsp;operating&nbsp;as desired, H3&nbsp;scheduled the go-live date&nbsp;to put the&nbsp;DataBC&nbsp;team back in the driver’s seat.&nbsp;&nbsp;</p>



<h3>Hands-On Experience&nbsp;</h3>



<p>Highway Three used&nbsp;<a href="https://www.highwaythreesolutions.com/cloud-migration-hub" target="_blank" rel="noreferrer noopener"><strong>Atlassian Cloud</strong></a>&nbsp;to manage the migration, leveraging the powerful epics feature of&nbsp;<a href="https://www.highwaythreesolutions.com/products/jira" target="_blank" rel="noreferrer noopener"><strong>Jira</strong></a>&nbsp;to create hierarchical user stories;&nbsp;<a href="https://www.highwaythreesolutions.com/products/confluence" target="_blank" rel="noreferrer noopener"><strong>Confluence</strong></a>&nbsp;to house planning documents and project requirements; and an instance of&nbsp;<a href="https://www.highwaythreesolutions.com/products/jira-service-management" target="_blank" rel="noreferrer noopener"><strong>Jira Service Management</strong></a>&nbsp;to facilitate feedback and bug reports from all the teams being migrated.&nbsp;&nbsp;&nbsp;</p>



<h3>Looking Back to Move Forward&nbsp;</h3>



<p>As this project was broken down into three different phases to&nbsp;migrate&nbsp;DataBC’s&nbsp;ten agile teams with minimal disruption, Highway Three took a&nbsp;retrospective approach to refine each migration:&nbsp;using learnings from the previous instance&nbsp;to inform and improve the next. This&nbsp;iterative&nbsp;approach eliminated&nbsp;most of the&nbsp;bugs before&nbsp;the move, with the final migration being completed essentially bug-free, with little&nbsp;—&nbsp;if&nbsp;any&nbsp;—&nbsp;downtime.&nbsp;&nbsp;</p>



<h3>Security Strategy&nbsp;</h3>



<p>In a cloud-server environment, security&nbsp;plays a vital role. To help the client&nbsp;create and maintain a more secure environment, Highway Three&nbsp;organized a comprehensive security&nbsp;cleanup&nbsp;and documented a&nbsp;best-practices onboarding process in Confluence,&nbsp;including&nbsp;a three-step how-to,&nbsp;making&nbsp;it easier for their team to onboard users quickly and effectively.&nbsp;&nbsp;</p>



<h3>Delivering the Learning</h3>



<blockquote class="wp-block-quote"><p>With the cloud version of Jira, we don&#8217;t have to worry about the service being down or assigning someone to implement future versions.  Instead, our teams can focus on using the software the way it was intended:  managing projects, running sprints, and facilitating our version of agile.</p><cite>Team Lead, Business Analysis &amp; Project Management, Data Services </cite></blockquote>



<p>As the&nbsp;DataBC&nbsp;team was&nbsp;already&nbsp;comfortable&nbsp;with Jira,&nbsp;they didn’t require the typical training offered&nbsp;when migrating from server to cloud, so the H3 team was able to show some advanced use cases,&nbsp;tools, and&nbsp;advice and guidance&nbsp;to ease the migration of the experienced users from the on-prem&nbsp;server to their new cloud environment.&nbsp;These workshops, like most of the Highway Three&nbsp;training sessions,&nbsp;were recorded to ensure the&nbsp;information&nbsp;is&nbsp;available for review&nbsp;as needed and&nbsp;accessible&nbsp;for future team&nbsp;members&nbsp;as they&nbsp;join the crew.&nbsp;</p>



<p>For teams new to Jira,&nbsp;the H3&nbsp;training&nbsp;typically covers the topics and challenges the users might encounter, such as&nbsp;the differences between navigation and profile management,&nbsp;with&nbsp;tips and shortcuts&nbsp;that most clients love&nbsp;to use because they make their lives much easier.&nbsp;&nbsp;</p>



<h2>Post-Migration Support&nbsp;</h2>



<p>While it might seem that a cloud migration is a one-and-done experience, Highway Three has found that following a migration, there are opportunities to improve your processes and reconsider how much energy is being spent to manage your Jira instance.&nbsp;By&nbsp;completing&nbsp;team-by-team&nbsp;mini-workshops,&nbsp;the&nbsp;H3&nbsp;team&nbsp;can evaluate how the organization&nbsp;is using Jira&nbsp;and&nbsp;how it’s working&nbsp;from a technical perspective,&nbsp;followed by recommendations&nbsp;about&nbsp;what can be done to improve performance&nbsp;and productivity. These&nbsp;mini-workshops&nbsp;are a great way to share&nbsp;Jira best practices and&nbsp;tips’n&nbsp;tricks the Highway Three&nbsp;team&nbsp;has discovered or created over the years.&nbsp;</p>



<p><strong>Managed services and professional support with an ongoing relationship from an experienced partner, like Highway Three, can provide answers to questions, offer recommendations, and make configuration changes as needed.&nbsp;</strong>&nbsp;</p>



<p><strong>If you’d like to&nbsp;improve productivity, speed, and performance for your team, download this whitepaper to&nbsp;learn&nbsp;the&nbsp;</strong><a rel="noreferrer noopener" href="https://www.highwaythreesolutions.com/news/5-reasons-to-move-to-jira-cloud" target="_blank"><strong>Top 5 Reasons to Move to Jira Cloud</strong></a>&nbsp;</p>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:100%">
<div class="wp-block-columns">
<div class="wp-block-column">
<h3>Challenges</h3>



<ul><li>On-prem&nbsp;server&nbsp;was multiple versions behind&nbsp;current&nbsp;&nbsp;</li><li>Excessive staff-time&nbsp;was&nbsp;required to maintain&nbsp;the&nbsp;on-prem&nbsp;server&nbsp;</li><li>Substantial knowledge&nbsp;was&nbsp;housed in&nbsp;a&nbsp;single resource&nbsp;– who took a promotion with another team</li></ul>
</div>



<div class="wp-block-column">
<h3>Solutions</h3>



<ul><li>Automatic roll-out of&nbsp;new versions and functionality available in the cloud&nbsp;</li><li>Managed and monitored&nbsp;hosting allows clients&nbsp;and users to focus on their customers, not the software&nbsp;</li><li>Documented processes housed in Confluence provide an easy to maintain knowledge repository&nbsp;</li></ul>
</div>
</div>
</div>
</div>



<h2>Results</h2>



<ul><li>Server-uptime is a non-issue now&nbsp;</li><li>No concern about upgrading&nbsp;to future versions of Jira&nbsp;</li><li>Teams&nbsp;are able to&nbsp;focus on using the software for its intended purpose: managing projects and sprints&nbsp;</li><li>A stable and reliable solution&nbsp;that&nbsp;gives the&nbsp;DataBC&nbsp;team confidence in the tools they use&nbsp;on a daily basis&nbsp;</li></ul>


Case Study: Data Services Migration to Atlassian Cloud


<p><strong>On November 10, tune in to the Atlassian High Velocity: ITSM World Tour</strong>, a 2-hour digital broadcast featuring teams from the top of the charts.</p>



<ul><li>Learn how high-velocity IT teams fuel digital transformation</li><li>Deep dive into customer success stories, including&nbsp;Lufthansa, CBS, Ginkgo Bioworks, Saint-Gobain, and Belong</li><li>Get a demo of Jira Service Management’s latest features</li><li>Best part—no cover charge!</li></ul>



<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="https://www.youtube.com/playlist?list=PLaD4FvsFdarSZVpAN9t4V798ipI_9safq" target="_blank" rel="noreferrer noopener">Check out ITSM Videos from Atlassian</a></div>
</div>



<p><strong>About the event:</strong></p>



<ul><li><strong>What</strong>: Atlassian’s High Velocity: ITSM World Tour</li><li><strong>When</strong>: November 10th, 2021<ul><li>Broadcast 1: 8am &#8211; 10am PT / 5pm &#8211; 7pm CEST / 1am &#8211; 3am AEST</li><li>Broadcast 2: 5pm &#8211; 7pm PT / 2am &#8211; 4am CEST / 10am &#8211; 12pm AEST</li></ul></li></ul>



<p>The event also serves as a launchpad for the second edition of our ITSM Lightning Talk series. Registrants of the High Velocity: ITSM World Tour will be automatically registered for the Lightning Talks.</p>



<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="https://www.youtube.com/playlist?list=PLaD4FvsFdarSZVpAN9t4V798ipI_9safq" target="_blank" rel="noreferrer noopener">Check out ITSM Videos from Atlassian</a></div>
</div>



<p></p>


The Atlassian High Velocity: ITSM World Tour is coming!


<p>In this post, we will be discussing <a rel="noreferrer noopener" href="https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?hosting=cloud&amp;tab=overview" target="_blank">ScriptRunner for Jira</a>, an automation and customization app to enhance Jira functionality, developed by Adaptavist.</p>



<p>To learn more about the series, take a look at our introductory post: <a href="/blog/jira-app-migration-getting-ready-for-the-cloud" data-type="URL" data-id="/blog/jira-app-migration-getting-ready-for-the-cloud" target="_blank" rel="noreferrer noopener">Jira App Migration: Top 10 Apps Evaluated</a>.</p>



<p>To learn more about the differences in ScriptRunner for Jira Server verses Jira Cloud, refer to our blog post &#8211; <a href="/blog/the-scriptrunner-rundown" target="_blank" rel="noreferrer noopener">The ScriptRunner Rundown</a>.</p>



<hr class="wp-block-separator"/>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<div class="wp-block-columns are-vertically-aligned-center">
<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-large"><img loading="lazy" width="1024" height="605" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/cloud-vs-server-scriptrunner-thumbnail-1024x605.png" alt="" class="wp-image-38" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/cloud-vs-server-scriptrunner-thumbnail-1024x605.png 1024w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/cloud-vs-server-scriptrunner-thumbnail-300x177.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/cloud-vs-server-scriptrunner-thumbnail-768x454.png 768w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/cloud-vs-server-scriptrunner-thumbnail.png 1075w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure></div>
</div>



<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:66.66%">
<p>Even though there is some support and documentation available to help you with your migration, it is quite difficult to shift ScriptRunner data to the Cloud. ScriptRunner’s migration journey involves a lot of manual steps and has significant feature parity between environments.</p>
</div>
</div>



<figure class="wp-block-table is-style-h3-table"><table class="has-fixed-layout"><tbody><tr><td><strong>Feature</strong> <strong>Compatibility</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="83" class="wp-image-567" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/feature-compatibility-partial.png" alt="Partial"></td></tr><tr><td><strong>Migration Complexity</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="263" height="82" class="wp-image-571" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/migration-complexity-difficult.png" alt="Difficult"></td></tr><tr><td><strong>Migration Method</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="82" class="wp-image-573" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/migration-method-mixed.png" alt="Mixed"></td></tr><tr><td><strong>Migration Support Available</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="83" class="wp-image-576" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/migration-support-available-limited.png" alt="Limited"></td></tr><tr><td><strong>Supported Jira Migration Methods</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="82" class="wp-image-578" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/supported-jira-migration-methods-full-site-import.png" alt="Full Site Import"></td></tr></tbody></table></figure>



<hr class="wp-block-separator"/>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h3>Feature Compatibility</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>There are a lot of discrepancies between the features available in ScriptRunner’s Server and Cloud offerings. These differences are largely due to the fact that the fundamental architecture and execution strategy vary greatly between the two environments.</p>
</div>



<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-comparing-96.png" alt="" class="wp-image-590"/></figure></div>
</div>
</div>



<p>One of the most notable differences in Jira Cloud is it only offers a REST API and not a Java API like Jira Server; therefore, there are differences in the extension points that are available to use in the Atlassian Connect framework. Additionally, for implementations the plugins for the V2 framework are applied behind the firewall.</p>



<p>For a complete list of feature differences, refer to the <a href="https://docs.adaptavist.com/sr4jc/latest/scriptrunner-migration/feature-parity" target="_blank" rel="noreferrer noopener">Feature Parity table</a> provided by ScriptRunner.</p>



<p>Even though there is a significant difference in Server and Cloud features, be sure to check which features you would like migrated, as you may lose little to no functionality if the features that are not supported in Cloud are not presently used by your Server.</p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h3>Migration Method and Complexity</h3>



<div class="wp-block-columns">
<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-hard-to-find-96.png" alt="" class="wp-image-591"/></figure></div>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>Migrating ScriptRunner to the Cloud is a tedious process as you must first analyze if each script can be implemented with the native features in Cloud, then write pseudo code for the server script, and finally convert the code to a cloud script. After all of this, you can complete a full site import and add the scripts to your cloud site.</p>
</div>
</div>



<p>There is no support to migrate with the Jira Cloud Migration Assistant (JCMA) yet, though they are actively working with Atlassian. You can check the status by viewing the <a href="https://jira.atlassian.com/browse/MIG-524" target="_blank" rel="noreferrer noopener">public facing Atlassian Jira ticket</a>.<a href="https://jira.atlassian.com/browse/MIG-524"> </a></p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h3>Migration Support Available</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>Even though ScriptRunner’s migration journey is not straight-forward, there is a <a href="https://docs.adaptavist.com/sr4jc/current/scriptrunner-migration" target="_blank" rel="noreferrer noopener">migration guide</a> provided by Adaptavist to help you transition to the Cloud. For help with specific issues in your migration, you can always contact Adaptavist by submitting a <a href="https://productsupport.adaptavist.com/servicedesk/customer/portal/2/user/login?destination=portal%2F2" target="_blank" rel="noreferrer noopener">support request</a>.</p>
</div>



<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-service-96.png" alt="" class="wp-image-592"/></figure></div>
</div>
</div>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h2>Possible Challenges</h2>



<div class="wp-block-columns">
<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-warning-shield-96.png" alt="" class="wp-image-593"/></figure></div>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>The most challenging part about migrating ScriptRunner is analyzing each script that has been implemented in the Server and establishing a migration plan. While some of these script goals can be handled with Cloud features, others may need to converted to ScriptRunner Cloud Script.</p>
</div>
</div>



<p>Despite ScriptRunner for Jira Cloud only supporting a little over half of the features in Jira Server, Adaptavist continues to develop Cloud products and support more features in the Cloud environment.</p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/contact" target="_blank" rel="noreferrer noopener">Need help migrating ScriptRunner to the cloud? Contact us!</a></div>
</div>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<p><strong>Resources:</strong></p>



<ul><li><strong><a rel="noreferrer noopener" href="/blog/jira-app-migration-getting-ready-for-the-cloud" target="_blank">Highway Three Top 10 Apps Evaluated series</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?hosting=cloud&amp;tab=overview" target="_blank">ScriptRunner for Jira App</a></strong></li><li><strong><a href="/blog/the-scriptrunner-rundown" target="_blank" rel="noreferrer noopener">The ScriptRunner Rundown Blog Post</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://docs.adaptavist.com/sr4jc/latest/about-scriptrunner-for-jira-cloud/differences-between-scriptrunner-for-jira-server-and-jira-cloud" target="_blank">ScriptRunner for Jira Server verses Jira Cloud</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://docs.adaptavist.com/sr4jc/latest/scriptrunner-migration/feature-parity" target="_blank">Feature Parity Table</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://docs.adaptavist.com/sr4jc/current/scriptrunner-migration" target="_blank">Migration Guide</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://productsupport.adaptavist.com/servicedesk/customer/portal/2/user/login?destination=portal%2F2" target="_blank">Adaptavist Support</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://jira.atlassian.com/browse/MIG-524" target="_blank">JCMA integration Jira ticket</a></strong></li></ul>


ScriptRunner for Jira: Migration Evaluation


<p>In this post, we will be discussing the migration journey for <a rel="noreferrer noopener" href="https://marketplace.atlassian.com/apps/1212137/insight-asset-management?hosting=datacenter&amp;tab=overview" target="_blank">Insight &#8211; Asset Management</a> developed by Mindville and now acquired by Atlassian.</p>



<p>To learn more about the series, take a look at our introductory post: <a href="/blog/jira-app-migration-getting-ready-for-the-cloud" data-type="URL" data-id="/blog/jira-app-migration-getting-ready-for-the-cloud" target="_blank" rel="noreferrer noopener">Jira App Migration: Top 10 Apps Evaluated</a>.</p>



<hr class="wp-block-separator"/>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<div class="wp-block-columns are-vertically-aligned-center">
<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<figure class="wp-block-image size-large"><img loading="lazy" width="1024" height="351" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/insight-logo-1024x351.png" alt="" class="wp-image-860" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/insight-logo-1024x351.png 1024w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/insight-logo-300x103.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/insight-logo-768x263.png 768w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/insight-logo-1536x526.png 1536w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/insight-logo-2048x702.png 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
</div>



<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:66.66%">
<p>Migrating Insight data from Server to Cloud is an entirely manual process, as there are no supported Jira migration methods that are compatible. There is little to no information available on migrating Insight and it can be a time consuming and arduous process.</p>
</div>
</div>



<figure class="wp-block-table is-style-h3-table"><table class="has-fixed-layout"><tbody><tr><td><strong>Feature Compatibility</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="83" class="wp-image-567" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/feature-compatibility-partial.png" alt="Partial"></td></tr><tr><td><strong>Migration Complexity</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="263" height="82" class="wp-image-571" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/migration-complexity-difficult.png" alt="Difficult"></td></tr><tr><td><strong>Migration Method</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="83" class="wp-image-574" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/migration-method-manual.png" alt="Manual"></td></tr><tr><td><strong>Migration Support Available</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="263" height="83" class="wp-image-577" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/migration-support-available-insufficient.png" alt="Insufficient"></td></tr><tr><td><strong>Supported Jira Migration Methods</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="82" class="wp-image-580" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/supported-jira-migration-methods-na.png" alt="N/A"></td></tr></tbody></table></figure>



<hr class="wp-block-separator"/>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h3>Feature Compatibility</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>Many of the features available on Insight’s Server offering are available on Cloud; however, there are some features that are not currently available on Jira Cloud:</p>
</div>



<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-comparing-96.png" alt="" class="wp-image-590"/></figure></div>
</div>
</div>



<ul><li>Object schema templates</li><li>Reports</li><li>Widgets</li><li>Label Templates</li></ul>



<p>More details on the feature discrepancy between environments can be found in <a href="https://documentation.mindville.com/display/ICE/Feature+Comparison+-+Insight+Server+vs.+Cloud" target="_blank" rel="noreferrer noopener">this feature comparison</a>.</p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h3>Migration Method and Complexity</h3>



<div class="wp-block-columns">
<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-hard-to-find-96.png" alt="" class="wp-image-591"/></figure></div>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>Currently, there are no supported Jira migration methods, so you cannot migrate using a full site import or the Jira Cloud Migration Assistant (JCMA). For more updates, refer to <a href="https://jira.atlassian.com/browse/MIG-276" target="_blank" rel="noreferrer noopener">this Jira ticket</a>.</p>
</div>
</div>



<p>It appears that the only way to migrate Insight data to the Cloud is to manually input information in your Cloud instance.</p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h3>Migration Support Available</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>We discovered there is limited documentation available on migrating to the Cloud. Our recommendation would be to use the services of an Atlassian partner, like us, as we work closely with Atlassian and forget partnerships with app vendors, allowing us the ability to provide customized support.</p>
</div>



<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-service-96.png" alt="" class="wp-image-592"/></figure></div>
</div>
</div>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h2>Possible Challenges</h2>



<div class="wp-block-columns">
<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-warning-shield-96.png" alt="" class="wp-image-593"/></figure></div>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>Migrating Insight data is an entirely manual process which is time consuming and laborious to perform.</p>



<p>Ever since Atlassian’s announcement to end Server support, vendor companies and Atlassian are working together to make the migration journey for Jira apps more simpler.</p>
</div>
</div>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/contact" target="_blank" rel="noreferrer noopener">Need help migrating Insight to the cloud? Contact us!</a></div>
</div>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<p><strong>Resources:</strong></p>



<ul><li><strong><a href="/blog/jira-app-migration-getting-ready-for-the-cloud" target="_blank" rel="noreferrer noopener">Highway Three Top 10 Apps Evaluated series</a></strong></li><li><strong><a href="https://marketplace.atlassian.com/apps/1212137/insight-asset-management?hosting=datacenter&amp;tab=overview" target="_blank" rel="noreferrer noopener">Insight App</a></strong></li><li><strong><a href="https://documentation.mindville.com/category/inscloud" target="_blank" rel="noreferrer noopener">Insight for Jira Cloud Documentation</a></strong></li><li><strong><a href="https://documentation.mindville.com/display/ICE/Feature+Comparison+-+Insight+Server+vs.+Cloud" target="_blank" rel="noreferrer noopener">Insight Feature Comparison Server vs. Cloud</a></strong></li><li><strong><a href="https://jira.atlassian.com/browse/MIG-276?error=login_required&amp;error_description=Login+required&amp;state=1095eb30-9d46-4981-9b7f-684e269488b6" target="_blank" rel="noreferrer noopener">Jira ticket for Insight Migration Support</a></strong></li></ul>



<p></p>


Insight for Jira: Migration Evaluation


<p class="has-text-align-center"><meta charset="utf-8"><strong>Date:</strong> <em>Fri, Sep 17, 12:00 PM (PDT)</em></p>



<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/contact?subject=blog-vancouver-ace-september" target="_blank" rel="noreferrer noopener">Learn more about potential pitfalls in cloud migrations</a></div>
</div>



<figure class="wp-block-embed aligncenter is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe loading="lazy" title="&quot;Avoiding Potential Pitfalls in your Cloud Migration&quot; - Vancouver ACE September" width="500" height="281" src="https://www.youtube.com/embed/laGGM0vT_Io?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div></figure>



<h2><meta charset="utf-8">About this event</h2>



<p>Hello all,</p>



<p>Hope everyone has had a good and safe summer.&nbsp;</p>



<p>We are back with another presentation from Highway Three Solutions coming up starting at noon, September 17th.</p>



<p>We will be discussing tips and tricks on how to avoid common pitfalls with your organization&#8217;s Cloud migrations of your Atlassian suite.</p>



<p>Any organization with their Cloud migration still looming will no doubt benefit from the conversation.</p>



<p>Here is the presentation synopsis:</p>



<p><em>Highway Three Solutions will provide an update on Jira server to cloud migrations with the latest information from Atlassian and updates on the tools available to assist with the process. We’ll go through some real examples from our recent client migrations with and give you valuable information on how to avoid common pitfalls. We will focus on the technical and process challenges we faced, specifically issues with the JCMA, app migrations, data consolidation, user migration, and cloud security.</em></p>



<p>A Q&amp;A session will follow.</p>



<p>While we are looking forward to getting back to in person events as soon as it is safe to do so, we will be presenting this event virtually once again. Remember no Zoom link is required.&nbsp;Just log in with your Atlassian account, jump to the community page to join in at lunchtime on September 17th. Please reach out if you have any questions or problems, let us know and we&#8217;ll be happy to help.</p>



<p>Hope you can join us.</p>



<p>Thank you and stay safe.</p>



<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/contact?subject=blog-vancouver-ace-september" target="_blank" rel="noreferrer noopener">Learn more about potential pitfalls in cloud migrations</a></div>
</div>



<h2><meta charset="utf-8">Speakers</h2>



<p><meta charset="utf-8"><strong>Karen Fishwick</strong></p>



<p><em>Senior Systems Architect and Atlassian Specialist, Highway Three Solutions</em></p>



<p>Karen Fishwick is a Senior Systems Architect and Atlassian Specialist, as well as a founder of Highway Three Solutions. She is an Atlassian Certified Professional (ACP) and holds an undergraduate degree in Physics, with over 20 years&#8217; experience leading technical teams to create value driven project outcomes.</p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<p><strong>Joanne Yo</strong></p>



<p><em>Canada Regional Lead, Atlassian</em></p>


Avoiding Potential Pitfalls in your Cloud Migration – Vancouver ACE September


<p class="has-text-align-center"><em>Download the presentation slides below.</em></p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<a href="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/09/webinar6_app_migration_deck.pdf" download data-download="Jira App Migration: Top 10 Apps Evaluated Webinar" class="wp-block-h3-block-h3-pdf-download h3-pdf-download">PDF</a>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<p>Here at Highway Three Solutions, we took a look at migrating ten of the most popular apps in the Atlassian Marketplace. In the process, we investigated the tools available to support migration and uncovered the limitations when migrating from Jira Server to Jira Cloud. We learned a lot.</p>



<p>Join us for this webinar and we will walk you through our evaluations, share our tips for planning your app migration, and recap the latest news from Atlassian on migrating to the cloud.</p>



<p>Have lunch on us! The first 20 people to register and attend will receive a free meal delivery voucher.</p>


Jira App Migration: Top 10 Apps Evaluated Webinar


<p>At Highway Three Solutions we took a look at migrating 10 of the most popular apps in the Atlassian Marketplace so we could find out more about the tools available to support migration and the limitations when migrating from Jira Server to Jira Cloud. We learned at lot, too much to share in a single post! Instead we will do a series of posts to share our evaluations.</p>



<p>In each blog post we will provide a summary of our analysis &#8211; true at the time of the blog post &#8211; on what we consider to be the five key aspects to consider when planning an app migration for your Atlassian Server to Cloud migration:</p>



<ul><li>Server vs Cloud Feature Compatibility</li><li>Migration Complexity</li><li>Migration Method</li><li>Migration Support Available</li><li>Supported Jira Migration Methods</li></ul>



<p>We will also share our insights on some of the challenges that we encountered.</p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<p>The following are the 10 apps we will evaluate:</p>



<ul><li><strong><a rel="noreferrer noopener" href="/blog/tempo-timesheets-server-to-cloud-migration" target="_blank">Tempo Timesheets  &#8211; Time Tracking &amp; Reports</a></strong></li><li><a rel="noreferrer noopener" href="/blog/biggantt-server-to-cloud-migration" data-type="URL" data-id="/blog/biggantt-server-to-cloud-migration" target="_blank"><strong>BigGantt &#8211; Gantt Chart for Jira</strong></a></li><li><a rel="noreferrer noopener" href="/blog/proforma-for-jira-migration-evaluation" data-type="URL" data-id="/blog/proforma-for-jira-migration-evaluation" target="_blank"><strong>ProForma: Forms and Checklist for Jira</strong></a></li><li><a rel="noreferrer noopener" href="/blog/jsu-automation-for-jira-workflows-migration-evaluation" data-type="URL" data-id="/blog/jsu-automation-for-jira-workflows-migration-evaluation" target="_blank"><strong>JSU Automation Suite for Jira Workflows</strong></a></li><li><strong><a rel="noreferrer noopener" href="/blog/insight-for-jira-migration-evaluation" data-type="URL" data-id="/blog/insight-for-jira-migration-evaluation" target="_blank">Insight &#8211; Asset Management</a></strong></li><li><a href="/blog/scriptrunner-for-jira-migration-evaluation" data-type="URL" data-id="/blog/scriptrunner-for-jira-migration-evaluation" target="_blank" rel="noreferrer noopener"><strong>ScriptRunner for Jira</strong></a></li><li>Bitbucket</li><li>Structure (App)</li><li>Xray Test Management for Jira</li><li>Zephyr Scale &#8211; Test Management for Jira</li></ul>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/contact" target="_blank" rel="noreferrer noopener">Need help migrating your apps?</a></div>
</div>


Jira App Migration: Top 10 Apps Evaluated


<p>In this post we share our assessment of migrating the app Tempo Timesheets, a time tracking and resource management tool developed by Tempo. The first thing to note is the functionality originally included in the Tempo Timesheets app has been separated into three different apps on Cloud: </p>



<ul><li><a href="https://marketplace.atlassian.com/apps/6572/tempo-timesheets-time-tracking-reports?hosting=cloud&amp;tab=overview" target="_blank" rel="noreferrer noopener"><strong>Tempo Timesheets</strong></a></li><li><a href="https://marketplace.atlassian.com/apps/1211881/tempo-planner-resource-planning?hosting=cloud&amp;tab=overview" target="_blank" rel="noreferrer noopener"><strong>Tempo Planner</strong></a></li><li><a href="https://marketplace.atlassian.com/apps/1221748/cost-tracker-for-tempo-timesheets?hosting=cloud&amp;tab=overview" target="_blank" rel="noreferrer noopener"><strong>Cost Tracker for Tempo Timesheets</strong></a></li></ul>



<p>Our review is for the <strong>Tempo Timesheets Cloud app.</strong></p>



<p><meta charset="utf-8">To learn more about the series, take a look at our introductory post: <a href="/blog/jira-app-migration-getting-ready-for-the-cloud" data-type="URL" data-id="/blog/jira-app-migration-getting-ready-for-the-cloud" target="_blank" rel="noreferrer noopener">Jira App Migration: Top 10 Apps Evaluated</a>.</p>



<hr class="wp-block-separator"/>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<div class="wp-block-columns">
<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-large"><img loading="lazy" width="1024" height="535" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/tempo-logo-1024x535.jpg" alt="" class="wp-image-450" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/tempo-logo-1024x535.jpg 1024w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/tempo-logo-300x157.jpg 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/tempo-logo-768x401.jpg 768w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/tempo-logo.jpg 1200w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure></div>



<p></p>
</div>



<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:66.66%">
<p class="has-text-align-left">Migrating Tempo Timesheets data has a few challenges, as it requires a knowledge of both automatic and manual migration methods; however, the documentation and resources available provide you with lots of support and guidance to complete your shift to the Cloud effectively.</p>
</div>
</div>



<figure class="wp-block-table aligncenter is-style-h3-table"><table class="has-fixed-layout"><tbody><tr><td class="has-text-align-left" data-align="left"><strong>Feature Compatibility</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="83" class="wp-image-567" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/feature-compatibility-partial.png" alt="Partial"></td></tr><tr><td class="has-text-align-left" data-align="left"><strong>Migration Complexity</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="263" height="82" class="wp-image-570" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/migration-complexity-medium.png" alt="Medium"></td></tr><tr><td class="has-text-align-left" data-align="left"><strong>Migration Method</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="82" class="wp-image-573" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/migration-method-mixed.png" alt="Mixed"></td></tr><tr><td class="has-text-align-left" data-align="left"><strong>Migration Support Available</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="83" class="wp-image-575" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/migration-support-available-substantial.png" alt="Substantial"></td></tr><tr><td class="has-text-align-left" data-align="left"><strong>Supported Jira Migration Methods</strong></td><td class="has-text-align-center" data-align="center"><img loading="lazy" width="264" height="82" class="wp-image-578" style="width: 150px" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/supported-jira-migration-methods-full-site-import.png" alt="Full Site Import"></td></tr></tbody></table></figure>



<div class="wp-block-columns">
<div class="wp-block-column">
<hr class="wp-block-separator"/>
</div>
</div>



<p>Read on for the details. </p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h3>Feature Compatibility</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>Even though Tempo Timesheets can be scripted to use the REST APIs available, the significant difference in the fundamental architecture between Server and Cloud makes it difficult to provide equivalent functionality in both environments. </p>
</div>



<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-comparing-96.png" alt="" class="wp-image-590"/></figure></div>
</div>
</div>



<p>While these APIs are synchronous and maintained in the Server, they are asynchronous and stateless in the Cloud. This makes it difficult to identify the results of what you have written to interact with the REST APIs.</p>



<p>Before migrating it is important to identify what features you use most and how your team may need to adapt when switching to Cloud. Most of the features available on Tempo Timesheets&#8217; server offering are available on Cloud with only a few exceptions: many of the Configuration options available on Server are not available on Cloud and there is no integration for <a href="https://github.com/tempo-io/tempo-events-example/blob/master/README.md" target="_blank" rel="noreferrer noopener">Event Handlers</a> on Cloud.</p>



<p>Also worth noting is many of the Features, Reports, and Configuration options are still <a href="https://help.tempo.io/cloud/en/tempo-server-migration-guide/server-data-center-vs--cloud--product-comparison/tempo-timesheets-server-data-center-vs--cloud.html" target="_blank" rel="noreferrer noopener">under development</a> for Cloud.</p>



<p>Features like Reports, Jira custom fields, and Time tracking are comparable between Server and Cloud with only a few differences. In most cases there are alternative methods of obtaining similar functionality for missing and partial features through the <a href="https://developer.atlassian.com/cloud/jira/platform/rest/v3/?utm_source=%2Fcloud%2Fjira%2Fplatform%2Frest%2F&amp;utm_medium=302#about" target="_blank" rel="noreferrer noopener">Tempo REST APIs</a>.</p>



<p>There are also advantages to Tempo Timesheets for Cloud over the server version with features like integrations for Chrome, Slack, and Visual Studio Code.</p>



<p>To learn more about the feature parity of Tempo Timesheets for Server and Cloud, take a look at this <a rel="noreferrer noopener" href="https://help.tempo.io/cloud/en/tempo-server-migration-guide/server-data-center-vs--cloud--product-comparison/tempo-timesheets-server-data-center-vs--cloud.html" target="_blank">Server and Cloud feature comparison</a>.</p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h3>Migration Method and Complexity</h3>



<div class="wp-block-columns">
<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-hard-to-find-96.png" alt="" class="wp-image-591"/></figure></div>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>Currently there is no support for the Jira Cloud Migration Assistant (JCMA), so the only way to migrate Tempo Timesheets data is to complete a full site import; however, Worklogs, Categories, and Timesheets are only partially migrated while Roles, Teams, Customers, and Accounts are not migrated at all.</p>
</div>
</div>



<p> In order to fully migrate these attributes, you will need to use <a href="https://apidocs.tempo.io/" target="_blank" rel="noreferrer noopener">Tempo Cloud REST APIs</a> and <a rel="noreferrer noopener" href="https://developer.atlassian.com/server/jira/platform/rest-apis/" target="_blank">Jira Server REST APIs</a>. You may also need to import .csv files or even update information manually on your cloud instance to complete your shift to Cloud.</p>



<p>Even though there is currently no support for the JCMA, at Highway Three we decided to investigate the steps it would take to migrate Tempo with the JCMA and what it would entail. To learn more about it, read our <a rel="noreferrer noopener" href="/blog/jira-tempo-cloud-migration" data-type="URL" target="_blank">Jira and Tempo Cloud Migration</a> blog post.</p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h3>Migration Support Available</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>Tempo has lots of documentation that can help you in your transition to the Cloud including steps to migrate, information on REST APIs, and details on Server and Cloud differences. Additionally, you can always contact Atlassian or Tempo to support your migration needs. A list of resources can be found at the end of our blog post.</p>
</div>



<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-service-96.png" alt="" class="wp-image-592"/></figure></div>
</div>
</div>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<h2>Possible Challenges</h2>



<div class="wp-block-columns">
<div class="wp-block-column is-vertically-aligned-center" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-full"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/08/icons8-warning-shield-96.png" alt="" class="wp-image-593"/></figure></div>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>We believe several challenges can arise when migrating from Server to Cloud for Tempo Timesheets. Tempo data in Jira Server is stored in the Jira server database while in Jira Cloud, data is stored in a vendor-specific storage. This difference of storage space may create complications in the Server to Cloud migration journey which can include worklogs not migrating automatically.</p>
</div>
</div>



<p>In our migration analysis, here are the issues we encountered that are important to note:</p>



<ul><li>You may have to wait up to 48 hours between each cloud site import &#8211; Tempo has to receive your request to reset and then carry through reset data. <strong>You cannot reset it yourself.</strong></li><li>It is important to understand how time zones will affect the availability of vendor support as assistance may not be active during your working hours.</li><li>Be sure to use an XML backup before you attempt a migration, even during testing.</li></ul>



<p>In order to provide a smoother migration experience, Tempo is working to make it possible for consumers to migrate Tempo Timesheets data with the JCMA and developing more REST APIs. More details on Tempo’s upcoming migration options can be found on their <a href="https://www.tempo.io/product-roadmap-server-to-cloud-migration" target="_blank" rel="noreferrer noopener">roadmap</a>.</p>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<div class="wp-block-buttons">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="https://www.highwaythreesolutions.com/contact" target="_blank" rel="noreferrer noopener">Need help migrating Tempo to the Cloud? Contact us!</a></div>
</div>



<div style="height:64px" aria-hidden="true" class="wp-block-spacer"></div>



<p><strong>Resources:</strong></p>



<ul class="has-black-color has-text-color"><li><strong><a href="/blog/jira-app-migration-getting-ready-for-the-cloud" target="_blank" rel="noreferrer noopener">Highway Three Top 10 Apps Evaluated series</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://marketplace.atlassian.com/apps/6572/tempo-timesheets-time-tracking-reports?hosting=cloud&amp;tab=overview" target="_blank">Tempo Timesheets App</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://tempo-io.atlassian.net/wiki/spaces/THC/pages/1372127383/Tempo+Server+Migration+Guide" target="_blank">Tempo Server Migration Guide</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://help.tempo.io/cloud/en/tempo-server-migration-guide/server-data-center-vs--cloud--product-comparison/tempo-timesheets-server-data-center-vs--cloud.html" target="_blank">Server and Cloud Feature Comparison</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://apidocs.tempo.io/" target="_blank">Tempo Cloud API documentation</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://developer.atlassian.com/server/jira/platform/rest-apis/" target="_blank">Jira Server REST API</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://www.highwaythreesolutions.com/blog/jira-tempo-cloud-migration" target="_blank">Jira and Tempo Cloud Migration blog post</a></strong></li><li><strong><a rel="noreferrer noopener" href="https://www.tempo.io/product-roadmap-server-to-cloud-migration" target="_blank">Tempo Roadmap</a></strong></li></ul>


Tempo Timesheets: Migration Evaluation


<p>In some organizations, product issues are tracked in multiple locations. This often occurs when internal and external teams collaborating on a single code base or a single project. Internal teams will often use a licensed product such as Jira Cloud; whereas, external and distributed teams tend to use free issue management solutions such as GitHub&#8217;s issues. These tightly coupled solutions are often extended by products like ZenHub which add additional project management capabilities to the basic system.</p>



<p>Using multiple issue trackers causes confusion for developers and project managers. Issues become duplicated across systems and cause confusion around what issues are the source of truth for the project. As a result, sprint planning and roadmap creation becomes difficult as the issues within them contain inaccurate data.</p>



<div class="wp-block-image is-style-h3-screenshot"><figure class="aligncenter size-large"><img loading="lazy" width="808" height="251" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/github_jira_sync.png" alt="" class="wp-image-125" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/github_jira_sync.png 808w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/github_jira_sync-300x93.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/github_jira_sync-768x239.png 768w" sizes="(max-width: 808px) 100vw, 808px" /></figure></div>



<p>We have worked with a few organizations within the public sector, one federal and one provincial, that encountered this very problem. Both scenarios were a result of the open source community engaging with product development.</p>



<p>Both organizations support open source projects hosted in GitHub. The internal project teams use Jira Cloud to manage their feature development and bug fixes, while also obtaining support from external users who use GitHub issues to raise tickets. The project team requested that issues raised in GitHub were also shown in Jira so that internal developers could plan their work. Additionally, external developers needed visibility into the product schedule and sprints.</p>



<h2>Enter, Exalate…</h2>



<p><em>Exalate is the most flexible synchronization tool and the leading Cross-Company Integration solution. Synchronize your Jira instances, ServiceNow, Zendesk, GitHub, Azure DevOps &amp; any other work management systems.</em></p>



<p>These projects used Exalate to sync issues between the GitHub and Jira projects enabling a close collaboration between teams. Below is a diagram explaining where Exalate sync fits into the two systems.</p>



<div class="wp-block-image is-style-h3-screenshot"><figure class="aligncenter size-large is-resized"><img loading="lazy" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-162046.png" alt="" class="wp-image-126" width="766" height="519" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-162046.png 1021w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-162046-300x203.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-162046-768x521.png 768w" sizes="(max-width: 766px) 100vw, 766px" /></figure></div>



<h2>Implementation Details</h2>



<p>It was important to easily identify what issues came from which source (Github or Jira). We were able to meet this requirement by using card layout and colors to clearly indicate which issues are synced with GitHub.</p>



<p>The internal Jira project integrated with around 30 different GitHub repositories. This means that not only did the internal team need to know what issues were from GitHub vs Jira, they also needed to know what repository the GitHub issues were raised against.</p>



<div class="wp-block-columns">
<div class="wp-block-column">
<p>We chose to use Jira components to distinguish between internal Jira issues and external GitHub issues. The component was applied using Jira Automation.</p>



<p>A custom field indicating the GitHub repository was added to the issue types in Jira and was automatically synced during the Exalate updates.</p>



<p>These two fields were displayed on the board cards so that Jira Developers can quickly and easily see where the Github Issues originated from.</p>
</div>



<div class="wp-block-column">
<figure class="wp-block-image size-large is-style-h3-screenshot"><img loading="lazy" width="914" height="623" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-161837.png" alt="" class="wp-image-128" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-161837.png 914w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-161837-300x204.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-161837-768x523.png 768w" sizes="(max-width: 914px) 100vw, 914px" /></figure>
</div>
</div>



<p>Another small gotcha, is that GitHub issues don’t currently support custom fields. This means that Jira fields like issue type and sprint values had to be synced to GitHub labels.</p>



<p>Because Jira and Github have significant differences in the fields they support, and because we don’t necessarily want to expose all of the Jira activity in Github, we chose to expose certain updates using Automation for Jira. As an example, we were able to add a comment when the issue status changed. That comment was then sync’d between the two issues so that in GitHub you would see the update. It would look something like this:</p>



<div class="wp-block-image is-style-h3-screenshot"><figure class="aligncenter size-large is-resized"><img loading="lazy" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-161613.png" alt="" class="wp-image-129" width="524" height="73" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-161613.png 699w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/image-20210114-161613-300x42.png 300w" sizes="(max-width: 524px) 100vw, 524px" /></figure></div>



<p>The clients have been using this system for about 3 months and have been very happy with Exalate and the ability it gives them.</p>



<p>Our tips for a successful Exalate implementation: keep the synchronization as simple as possible and use Jira Automation to bridge any gaps. This is because updating the exalate configuration is harder than updating an automation rule. It also tends to lead to a more robust setup and the integration point is stronger.</p>



<h2>Summary</h2>



<p>Other than choosing a project name, communication about features and bugs is possibly one of the most difficult issues in software development. Exalate gave these public sector organizations the ability to automate the communication of development and status between the internal and the open source communities. This is just one of the many use cases for Exalate and their extremely supportive team; through out these implementations the people at <a rel="noreferrer noopener" href="https://exalate.com/" target="_blank">Idalko/Exalate</a> have been very helpful in diagnosing and providing a workaround for a bug within the Github system.</p>



<p>If you or your organization are experiencing difficulties communicating Jira issues between different systems or teams reach out to see what we, and Exalate, can do for you.</p>



<div class="wp-block-buttons is-content-justification-center">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/contact" target="_blank" rel="noreferrer noopener">Contact Us</a></div>
</div>


Jira and Github, an Exalate Case Study


<div class="wp-block-buttons is-content-justification-center">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/webinars?id=jira-in-the-cloud-versions" target="_blank" rel="noopener">Watch now</a></div>
</div>



<p>With Atlassian&#8217;s recently announced plan to end support for server products, most companies plan to make the move to Atlassian cloud. Migrating to any cloud environment can be daunting, and many users are wondering where to start.</p>



<p>The first step in your cloud migration journey is to figure out which cloud version is right for your organization. In this webinar, we will guide you through your options. From cloud free to cloud enterprise, we will discuss what is included, who it is suitable for, and the pros and cons of each version so that you know which version is best for you.</p>



<figure class="wp-block-image size-large"><img loading="lazy" width="1024" height="427" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/webinar_cloud_versions-1024x427.jpeg" alt="" class="wp-image-55" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/webinar_cloud_versions-1024x427.jpeg 1024w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/webinar_cloud_versions-300x125.jpeg 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/webinar_cloud_versions-768x320.jpeg 768w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/webinar_cloud_versions.jpeg 1514w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>



<div class="wp-block-buttons is-content-justification-center">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/webinars?id=jira-in-the-cloud-versions" target="_blank" rel="noopener">Watch Now</a></div>
</div>


Jira Cloud Migration: Cloud Versions


<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>Using <a href="https://www.adaptavist.com/products/atlassian-apps/scriptrunner-for-jira" target="_blank" rel="noreferrer noopener">Adaptavist ScriptRunner for Jira Server</a> is much like souping-up a car. Sometimes, it can even seem as magical as Dr. Brown&#8217;s DeLorean from Back to the Future. With the announcement from Atlassian to move away from server and focus solely on cloud, we have to wonder if ScriptRunner for Jira Cloud is going to match up to its predecessor.</p>
</div>



<div class="wp-block-column" style="flex-basis:33.33%">
<figure class="wp-block-image size-large"><img loading="lazy" width="570" height="329" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/YTM5YmY0NGMtYmUyMS00ZmM5LWFmOWEtZTAwZjFiYzk0ODkz_supercharge-your-customer-support-portal-with-scriptrunner.png" alt="" class="wp-image-78" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/YTM5YmY0NGMtYmUyMS00ZmM5LWFmOWEtZTAwZjFiYzk0ODkz_supercharge-your-customer-support-portal-with-scriptrunner.png 570w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/YTM5YmY0NGMtYmUyMS00ZmM5LWFmOWEtZTAwZjFiYzk0ODkz_supercharge-your-customer-support-portal-with-scriptrunner-300x173.png 300w" sizes="(max-width: 570px) 100vw, 570px" /></figure>
</div>
</div>



<p>There are significant differences between how add-ons can integrate with Atlassian Cloud versus Server. The server versions of Atlassian&#8217;s products allow apps (i.e. add-ons) to run on the same machines, create databases specific to the app instance, and interact with the lowest level API. With Atlassian Cloud, add-on developers are limited to running code within the users&#8217; browser (via Javascript) or on their own servers; the only integration points are through the Atlassian Cloud REST APIs.</p>



<p>While some ScriptRunner for Jira Server functionality can be re-written to interact with the Cloud REST API rather than the low-level Java API, porting to Cloud is more than simply translating from one API to another. The shift from Server to Cloud is also a change in the fundamental architecture, where the key characteristics of state and synchronicity shift. In the server environment, API requests were synchronous (i.e. requests wait for a response) and state was maintained. In the cloud environment, REST APIs, are asynchronous and stateless. Put another way: the results of script execution may not be visible or evident within the UI immediately.</p>



<p>As a result of the shift to cloud, an app is no longer able to fully integrate with all aspects of the Atlassian product. This change in architecture has forced ScriptRunner to drastically alter what they provide for Atlassian Cloud products.</p>



<p>The remainder of this article summarizes the limitations of ScriptRunner for Jira Cloud.</p>



<h2>ScriptRunner for Atlassian Cloud Limitations</h2>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:33.33%">
<figure class="wp-block-image size-large"><img loading="lazy" width="672" height="1024" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_264365357-672x1024.jpg" alt="" class="wp-image-79" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_264365357-672x1024.jpg 672w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_264365357-197x300.jpg 197w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_264365357-768x1170.jpg 768w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_264365357-1008x1536.jpg 1008w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_264365357-1344x2048.jpg 1344w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_264365357-scaled.jpg 1680w" sizes="(max-width: 672px) 100vw, 672px" /></figure>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>We have grouped the differences between Server and Cloud into the following categories:</p>



<ul><li>System Level</li><li>User Related Actions</li><li>JQL Function Limitations</li><li>ScriptRunner Features</li></ul>



<p>For each category we will outline the features that are not currently supported in ScriptRunner for Atlassian Cloud.</p>
</div>
</div>



<h3>System Level</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>System Level features are related to database connections, mail handlers, server logs, and system configurations. At this time the Jira Cloud API does not offer the same low-level access as Jira Server and this limitation affects the following ScriptRunner system level features:</p>
</div>



<div class="wp-block-column" style="flex-basis:33.33%">
<figure class="wp-block-image size-large"><img loading="lazy" width="1024" height="1024" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1645966345-1024x1024.png" alt="" class="wp-image-80" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1645966345-1024x1024.png 1024w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1645966345-300x300.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1645966345-150x150.png 150w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1645966345-768x768.png 768w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1645966345-1536x1536.png 1536w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1645966345-2048x2048.png 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
</div>
</div>



<div class="wp-block-columns">
<div class="wp-block-column">
<ul><li>Resources: Database Connection</li><li>Resources: Local Database Connection</li><li>Code Insights</li><li>Script Fields: Database picker</li><li>Script Fields: Remote issue(s) picker</li></ul>
</div>



<div class="wp-block-column">
<ul><li>Re-index Issues</li><li>Built-In: View Server Log Files</li><li>Built-In: Configuration Exporter</li><li>Built-In: Copy Project</li><li>Built-In: Config Exporter</li></ul>
</div>



<div class="wp-block-column">
<ul><li>Built-In: Copy Project</li><li>Built-In: Config Exporter</li><li>Built-In: Clear Groovy Classloader or Jira Internal Caches</li><li>Built-In: Configuration Exporter</li><li>Built-In: View Server Log Files</li></ul>
</div>
</div>



<h3>User Related Actions</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:33.33%">
<figure class="wp-block-image size-large"><img loading="lazy" width="738" height="738" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_266711807.png" alt="" class="wp-image-81" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_266711807.png 738w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_266711807-300x300.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_266711807-150x150.png 150w" sizes="(max-width: 738px) 100vw, 738px" /></figure>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>Systems with managed accounts can connect to a User Directory (LDAP, etc.); however, functionality available for scripting user management in Cloud is very different than on Server. ScriptRunner for Server can interact with these types of integrations (LDAP integration points). Specifically, ScriptRunner for Server can:</p>



<ul><li>Interact with LDAP connection resources</li><li>Connect picker fields to LDAP details (e.g. to select from a list of users)</li><li>Switch to a different user</li></ul>
</div>
</div>



<p>None of the above is possible with ScriptRunner for Cloud. It is possible for a user to masquerade as another user if you have the right system permissions, but this is not something you can programatically do with ScriptRunner for Cloud.</p>



<h3>JQL Functions</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>ScriptRunner for Server can interact directly with JQL queries. This is NOT possible for Cloud. As a result, many of the custom JQL functions previously possible for Server cannot be replicated for Cloud. However, ScriptRunner (in the background) can augment Jira issues with extra attributes that you can query within JQL. For example, when sprint information is updated for a project, a ScriptRunner script can update issues asynchronously with a keyword nextSprint.</p>
</div>



<div class="wp-block-column" style="flex-basis:33.33%">
<figure class="wp-block-image size-large"><img loading="lazy" width="624" height="682" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_748886182.png" alt="" class="wp-image-82" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_748886182.png 624w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_748886182-274x300.png 274w" sizes="(max-width: 624px) 100vw, 624px" /></figure>
</div>
</div>



<p>The following are the JQL functions that are not currently available via the Jira Cloud REST API:</p>



<div class="wp-block-columns">
<div class="wp-block-column">
<ul><li>aggregateExpression</li><li>completeInSprint</li><li>earliestUnreleasedVersionByReleaseDate</li><li>hasRemoteLinks</li><li>inactiveUsers</li><li>incompleteInSprint</li></ul>
</div>



<div class="wp-block-column">
<ul><li>jiraUserPropertyEquals</li><li>lastUpdated</li><li>linkedIssuesOfAll</li><li>linkedIssuesOfAllRecursive</li><li>linkedIssuesOfAllRecursiveLimited</li><li>linkedIssuesOfRemote</li></ul>
</div>



<div class="wp-block-column">
<ul><li>myProjects</li><li>overdue</li><li>recentProjects</li><li>releaseDate</li><li>removedAfterSprintStart</li><li>startDate</li></ul>
</div>
</div>



<h3>ScriptRunner Behaviours and Fragments</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:33.33%">
<figure class="wp-block-image size-large"><img loading="lazy" width="472" height="512" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/innovation.png" alt="" class="wp-image-83" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/innovation.png 472w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/innovation-277x300.png 277w" sizes="(max-width: 472px) 100vw, 472px" /></figure>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>The Behaviours feature included in ScriptRunner for Jira Server Behaviours provides more control over fields and their behaviours. This feature is not available for Cloud given the change in architecture and developer framework. It is not possible to interact and modify the UI in the same manner as with Jira Server, and this directly impacts manipulation of the Jira fields.</p>
</div>
</div>



<p>The ScriptRunner for Server Fragments feature allowed scripts to inject UI components within specific places. In Jira Cloud, the Atlassian developer framework provides specific areas of the page (i.e. screen) where add-ons can present data (UI components). Script Fragments in ScriptRunner for Cloud can only inject html in the web panels.</p>



<h2>Conclusion</h2>



<p>This may sound like it’s all bad news. It isn’t. The changes that come with the shift to Atlassian Cloud provide many advantages and new opportunities for add-on app developers. Adaptavist, the developers of ScriptRunner, have summarized this best:</p>



<blockquote class="wp-block-quote is-style-h3-blockquote"><p><em>As with most programming situations there are trade offs when writing scripts for both Cloud and Server and the limitations of Cloud are at the expense of stability and performance of the Atlassian application.</em></p></blockquote>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>The good news is that Adaptavist is continuing to develop ScriptRunner for Atlassian Cloud products. At present, just over half of the features in ScriptRunner for Jira Server are supported in some capacity in ScriptRunner for Jira Cloud. Their status page suggests they aren’t finished with this work yet and more changes are expected.</p>
</div>



<div class="wp-block-column" style="flex-basis:33.33%">
<figure class="wp-block-image size-large"><img loading="lazy" width="1024" height="757" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1515834812-1024x757.png" alt="" class="wp-image-84" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1515834812-1024x757.png 1024w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1515834812-300x222.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/shutterstock_1515834812-768x568.png 768w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
</div>
</div>



<p>Furthermore, the lack of supported features from the server version does not mean you will lose half of your functionality by moving to the cloud. The missing features may not be ones you currently use. We recommend you take stock of your existing ScriptRunner scripts in use and review them with the functionality supported in ScriptRunner for Cloud to identify the impact on your team. As an Atlassian solutions partner, we are here to support you with this analysis – if you need support then contact us.</p>



<p>If you would like to learn more about ScriptRunner, visit Adaptavist’s&nbsp;<a href="https://docs.adaptavist.com/?_ga=2.101774657.1335031310.1620160332-430693690.1618503562">new documentation site</a>&nbsp;or take a look at their&nbsp;<a href="https://scriptrunner.adaptavist.com/latest/jira/quickstart.html">previous location for documentation</a>&nbsp;for ScriptRunner up to version 6.20.0.</p>


The ScriptRunner Rundown


<p><a rel="noreferrer noopener" href="https://tractionguest.com/" target="_blank">Traction Guest</a> Enjoys High-Speed, Friction-Free Conversion to JIRA and Confluence.</p>



<p>Traction Guest is an industry leader in enterprise visitor management, making on-site experiences for employees and guests safe, secure, and effortless. With offices in Vancouver, Seattle, and Dublin, they needed a cohesive cloud platform with the ability to keep up with their agile development process.</p>



<p>Al Henry joined Traction Guest in 2019 and was tasked with enhancing the agile approach for their development team, featuring scrums, ceremonies, and sprints. He&#8217;d had experience with Jira in a previous organization, but Traction Guest was using a modified version of another work management platform. After realizing that the promised benefits of the current platform didn&#8217;t balance out the workarounds necessary to make it effective in an agile environment, and aggravated by a lack of visibility and reporting capacity, Al recommended an upgrade to Atlassian Cloud to take advantage of the power of Jira and Confluence.</p>



<div class="wp-block-image"><figure class="aligncenter size-large is-resized"><img loading="lazy" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Agile-Project-Management-1024x949.png" alt="" class="wp-image-108" width="512" height="475" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Agile-Project-Management-1024x949.png 1024w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Agile-Project-Management-300x278.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Agile-Project-Management-768x712.png 768w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Agile-Project-Management.png 1054w" sizes="(max-width: 512px) 100vw, 512px" /></figure></div>



<h2>Imminent Deadline</h2>



<p>During the decision phase, the team discovered that the incumbent platform&#8217;s licensing was due for renewal in three weeks. As Al had a proposal in place with <a rel="noreferrer noopener" href="https://www.highwaythreesolutions.com/" target="_blank">Highway Three Solutions</a>, he reached out to them to see if they could implement the conversion on a highly compressed timeline: he&#8217;d need a week to prepare for the migration, leaving only two weeks to install, update, and test the Atlassian cloud installation.</p>



<p>Highway Three Solutions responded by having two of their key professionals construct a project plan to convert before the end of the month. Traction Guest approved the plan, opting for a cloud solution to eliminate any on-prem performance concerns, and began the migration preparation process.</p>



<p>During the migration, the Traction Guest team discovered that despite having admin access through the previous PM resource, they couldn&#8217;t actually see all of their projects, resulting in a few being skipped in the data mapping process. With Highway Three&#8217;s help, Al and his team were able to recalibrate and resynchronize, getting access to the previously unseen data without losing essential components.</p>



<p><em>&#8220;We did have one glitch during the migration, and the Highway Three team took care of it for us,” </em>explained Al. <em>“They contacted Atlassian, submitted and managed the ticket, and helped us recover from the issue. They were very effective in resolving our issues!”</em></p>



<p>The Highway Three team implemented the plan, converted the database, integrated with Aha!, and the Traction Guest team was up and running with Jira on the first of the month.</p>



<blockquote class="wp-block-quote is-style-h3-blockquote"><p>Highway Three Solutions&#8217; professionalism and attention to detail was evident as the teams worked together to deliver the project on time. Our experience with Highway Three Solutions is a beneficial one as we work together to maintain the new Jira system and look to continuously improve our processes with their assistance.</p></blockquote>



<h2>Moving Forward</h2>



<p>Traction Guest&#8217;s primary focus was getting Jira up and working, integrating it into the development process. <em>&#8220;We haven&#8217;t made full use of Confluence yet,&#8221;</em> shared Al, <em>&#8220;but our support structure is now using it to house our runbooks and support documentation for triaging incidents, and our strike teams are using Confluence to house documentation about new-feature implementations.&#8221;</em> Confluence provides a central repository, which is much easier to use and manage than Traction Guest&#8217;s previous model that relied on Google Docs, Quip worksheets, and local storage. <em>&#8220;The searching capability of Confluence makes it a powerful tool for our teams,&#8221;</em> said Al, <em>&#8220;and we&#8217;re working on some training sessions to help everyone get up to speed with it.&#8221;</em></p>



<p>With six months of experience on the new platform, Al and his team are very pleased with the support, training, and advice from the Highway Three team, sharing <em>&#8220;they&#8217;re a great consulting team, and I appreciate that it feels like we work together on things, as opposed to us reaching out and merely contracting them to do the work.”</em></p>



<div class="wp-block-columns">
<div class="wp-block-column">
<h3>Challenges</h3>



<ul><li>Multiple workarounds to make incumbent project management tool fit desired agile process</li><li>Poor visibility into projects and reports</li><li>Various versions and locations of essential documentation</li><li>Highly compressed window to implement transition to Jira</li></ul>
</div>



<div class="wp-block-column">
<figure class="wp-block-image size-large"><img loading="lazy" width="1024" height="832" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Board-game-1024x832.png" alt="" class="wp-image-109" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Board-game-1024x832.png 1024w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Board-game-300x244.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Board-game-768x624.png 768w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Board-game.png 1255w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
</div>
</div>



<div class="wp-block-columns">
<div class="wp-block-column">
<figure class="wp-block-image size-large"><img loading="lazy" width="1024" height="904" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Computer-1024x904.png" alt="" class="wp-image-110" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Computer-1024x904.png 1024w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Computer-300x265.png 300w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Computer-768x678.png 768w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Computer.png 1246w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
</div>



<div class="wp-block-column">
<h3>Solutions</h3>



<ul><li>Implemented a complete migration to Atlassian Cloud, including Jira, Confluence, and JSM</li><li>Migration completed in less than two weeks with maximum communications</li><li>Implemented standardized scrum processes to provide planning and tracking across teams</li><li>Capitalized on Jira’s reporting capabilities to communicate planning and status to management team</li></ul>
</div>
</div>



<h2>Results</h2>



<ul class="h3-checkbox-list"><li>Jira dashboards, filters, and formats to provide a customized view of current projects</li><li>Effective isolation between different strike teams</li><li>Consolidated, searchable repository for all documentation via Confluence</li><li>Seamless integration with Aha! Roadmaps and collaboration tools</li><li>Strong relationship with Highway Three Solutions for training and support for Atlassian products</li></ul>



<p></p>


Case Study: Traction Guest’s Friction Free Conversion to Jira


<p>ScriptRunner can extend the functionality of Atlassian products, such as Confluence and Jira Software. From creating pages or tickets within the script console to setting up jobs and listeners, ScriptRunner is an excellent add-on.</p>



<p>In our previous article, <a href="/blog/the-scriptrunner-rundown" data-type="URL" data-id="/blog/the-scriptrunner-rundown" target="_blank" rel="noreferrer noopener">The ScriptRunner Showdown</a>, we explored possible limitations of ScriptRunner for Atlassian’s Cloud products when compared to the capabilities available for their Server products. Essentially, Atlassian’s Server products allow for more actions than Cloud products, largely because Cloud products are restricted to the Cloud REST API while Server products have access to both the Server REST API and Java REST API.</p>



<p>Our script uses a simple example, but one that is likely to be at the heart of much more complicated scripts: create a page. To make things a bit interesting, and to diverge from the ‘copy page tree’ built-in script provided by ScriptRunner, we want the new page to appear under the home page of the target space page hierarchy. In our example script the space key is&nbsp;<code>TESTSPACE</code>.</p>



<h2>Create a page script with ScriptRunner for Confluence Server</h2>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-large"><img loading="lazy" width="181" height="184" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/server-icon-1829170068-1623798240379.png" alt="" class="wp-image-45"/></figure></div>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>It turns out there are actually two approaches that can be used to create a page using ScriptRunner for Confluence Server: via the Java REST API components or using the Server REST API. We will demonstrate both approaches.</p>
</div>
</div>



<h3>Using Confluence Server Java REST API Components</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>One way of creating a page in a space would be to use components from the Java REST API.</p>
</div>



<div class="wp-block-column" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-large"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Java.png" alt="" class="wp-image-46"/></figure></div>
</div>
</div>



<p>Confluence Server has been around for a while and there is plenty of documentation on the internet to assist with learning the broad scope of the Java REST API, whether through Atlassian community Q&amp;As or&nbsp;<a href="https://developer.atlassian.com/server/confluence/java-api-reference/">documentation</a>. This article will not provide any further background or explanation of the provided script example.</p>



<p>The following code example uses the&nbsp;<code>PageManager</code>&nbsp;and&nbsp;<code>SpaceManager</code>&nbsp;components found in the API to create a page in the space with key&nbsp;<code>TESTSPACE</code>:</p>



<pre class="wp-block-code language-groovy"><code>import com.atlassian.confluence.pages.Page
import com.atlassian.confluence.pages.PageManager
import com.atlassian.confluence.spaces.Space
import com.atlassian.confluence.spaces.SpaceManager
import com.atlassian.sal.api.component.ComponentLocator

def spaceManager = ComponentLocator.getComponent(SpaceManager)
def pageManager = ComponentLocator.getComponent(PageManager)
 
def spaceKey = "TESTSPACE"

def space = spaceManager.getSpace("${spaceKey}")
def homePage = space.getHomePage()
 
Page parentPage = pageManager.getPage(homePage.id);

Page page = new Page();
page.setSpace(space);
page.setParentPage(parentPage);
page.setTitle("Title of Page");
page.setBodyAsString("Body of page. Bolded text.");

parentPage.addChild(page);

pageManager.saveContentEntity(page, null, null);</code></pre>



<p>When creating a new page, the ‘set’ functions within the Page class (<a href="https://docs.atlassian.com/ConfluenceServer/javadoc/7.12.2/index.html?com/atlassian/confluence/pages/Page.html">API 7.12.2 documentation</a>) can be used to add values to the page being created. Recall that one requirement for this example is for the new page to be created below the homepage in the space page tree hierarchy. Therefore the new page must&nbsp;<code>setParentPage</code>&nbsp;as the homepage, and the homepage must add the new page as its child. This example does not care about the history of the new page so it can be saved with a context of null.</p>



<h3>Using Confluence Server REST API</h3>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:66.66%">
<p>The Confluence REST API Documentation may not seem as extensive as the Java REST API, but for our comparison it will get the same job done. The Confluence Server Developer even includes an example on how to create a new page.</p>
</div>



<div class="wp-block-column" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-large"><img loading="lazy" width="96" height="96" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/API-Gear.png" alt="" class="wp-image-47"/></figure></div>
</div>
</div>



<p>The following is the code to create a new page, using our requirements and the REST API:</p>



<pre class="wp-block-code language-groovy"><code>import com.atlassian.confluence.spaces.SpaceManager
import com.atlassian.confluence.spaces.Space
import groovy.json.StreamingJsonBuilder
import com.atlassian.sal.api.component.ComponentLocator

def spaceManager = ComponentLocator.getComponent(SpaceManager)

def server = 'YOUR SERVER BASE URL'
def authString = 'username:password'.getBytes().encodeBase64().toString()

def spaceKey = "TESTSPACE"

def space = spaceManager.getSpace("${spaceKey}")
def homePage = space.getHomePage()
 
def pageParams = &#91;
	title: "Title of Page",
	type: "page",
	space:&#91;
		key:"${spaceKey}"
	],
    ancestors: &#91;
       &#91;id:homePage.id]
    ],
    body: &#91;
        storage: &#91;
           value: "Body of page. Bolded text.",
           representation: "storage"
        ]
    ]
]

def createPageResult = new URL("${server}/rest/api/content").openConnection() as HttpURLConnection
createPageResult.requestMethod = 'POST'
createPageResult.setRequestProperty('Authorization', "Basic ${authString}")
createPageResult.doOutput = true
createPageResult.setRequestProperty('Content-Type', 'application/json;charset=UTF-8')
createPageResult.outputStream.withWriter('UTF-8') { new StreamingJsonBuilder(it, pageParams) }
createPageResult.connect()
log.warn"${createPageResult.getResponseCode()} created Page ${pageParams.title} for Space ${spaceKey}"
//Close POST
createPageResult.disconnect()</code></pre>



<p>Using the Server REST API involves more set up or configuration, specifically, the script must specify:</p>



<ul><li>The base URL of the instance</li><li>The credentials (username and password) of a user who has permission to create a page in the target space.</li></ul>



<p>In the Adaptavist ScriptRunner for Confluence’s console, this code will create a page identical to the one made by the components script shared above.</p>



<h2>Create a page script with ScriptRunner for Confluence Cloud</h2>



<div class="wp-block-columns">
<div class="wp-block-column" style="flex-basis:33.33%">
<div class="wp-block-image"><figure class="aligncenter size-large"><img loading="lazy" width="178" height="177" src="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Cloud-plain.png" alt="" class="wp-image-48" srcset="https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Cloud-plain.png 178w, https://wordpress.highwaythreesolutions.com/wp-content/uploads/2021/07/Cloud-plain-150x150.png 150w" sizes="(max-width: 178px) 100vw, 178px" /></figure></div>
</div>



<div class="wp-block-column" style="flex-basis:66.66%">
<p>Adaptavist ScriptRunner for Confluence Cloud includes a few example code snippets which are helpful to kickstart your introduction to the Cloud REST API. The code below is similar to ScriptRunner’s&nbsp;<code>Create page in space</code>, with a few changes to fit this example. As with the previous code snippets, this creates a page in the Confluence space with key&nbsp;<code>TESTSPACE</code>.</p>
</div>
</div>



<pre class="wp-block-code language-groovy"><code>def spaceKey = "TESTSPACE"
def createPageResult = post('/wiki/rest/api/content')
        .header('Content-Type', 'application/json')
        .body(&#91;
            space: &#91;
                    key: spaceKey
            ],
            status: "current",
            title: "Title of Page",
            type: "page",
            body: &#91;
                    storage: &#91;
                            representation: "storage",
                            value: "Body of page. Bolded text."
                    ]
            ]
        ])
        .asObject(Map).body</code></pre>



<p>Instead of requiring the base url and authentication be added into the console by the user, the&nbsp;<code>post</code>&nbsp;function applies the values associated with the Cloud instance. That’s great news as it means less work for the developer.</p>



<p>If you have seen the ScriptRunner console’s example, you may have noticed they use a body format&nbsp;<code>view</code>&nbsp;while this example has&nbsp;<code>storage</code>. Depending on what the body content of the page is will help determine which format should be used. The&nbsp;<a href="https://developer.atlassian.com/cloud/confluence/rest/api-group-content/#api-api-content-post">Confluence REST API</a>&nbsp;states only one body format should be used, and it includes a list to choose from in its example. Definitions for the body formats can be found in the&nbsp;<a href="https://docs.atlassian.com/ConfluenceServer/javadoc/7.12.2/com/atlassian/confluence/api/model/content/ContentRepresentation.html">Server ContentRepresentation class</a>.</p>



<h2>What did we learn?</h2>



<p>We have shown three possibilities to script creating a page in a Confluence space. By demonstrating a Server script that uses the Server REST API we were able to see how that is similar to what can be expected when migrating to the Cloud. We were also able to clearly see Server scripts based upon the Java REST API components will require considerable more re-development than ones using the Server REST API.</p>



<p>If you will continue to develop new scripts for Server, you should consider switching to the Server REST API as much as possible to reduce the effort required to convert the scripts when you migrate to the Cloud.</p>



<p>We have summarized our findings in the following table.</p>



<figure class="wp-block-table is-style-h3-table"><table><thead><tr><th>Method</th><th>Create Page</th><th>User Requirements</th></tr></thead><tbody><tr><td>Components</td><td>&#8211; Get and add Space<br>&#8211; Set values<br>&#8211; Get and add Parent Page<br>&#8211; Add Child Page to Parent Page<br>&#8211; Save configuration</td><td>&#8211; Space Key<br>&#8211; Permission to access Space and add Page</td></tr><tr><td>Server REST API</td><td>&#8211; Get Space<br>&#8211; Create parameters<br>&#8211; POST parameters</td><td>&#8211; Space Key<br>&#8211; Base URL<br>&#8211; Username<br>&#8211; Password<br>&#8211; Permission to access Space and add Page</td></tr><tr><td>Cloud REST API</td><td>&#8211; Create parameters<br>&#8211; POST parameters</td><td>&#8211; Space Key<br>&#8211; Permission to access Space and add Page</td></tr></tbody></table></figure>



<p>We know our example was very simple, but it does demonstrate key differences between the three approaches, what you can do in the short term, and how you can plan for the long term as you look towards your Cloud migration.</p>



<p>As part of your migration planning it is especially important to check if any components in a ScriptRunner script have an equivalent API call that can be made in Cloud. If there are none, then you may need to consider alternate designs and exploring other approaches, like Automation. Knowing what to expect and planning with that in mind will help smooth out your migration path.</p>



<div class="wp-block-buttons is-content-justification-center">
<div class="wp-block-button is-style-h3-cta-button"><a class="wp-block-button__link" href="/contact?subject=ScriptRunner for Cloud" target="_blank" rel="noopener">Need help configuring ScriptRunner for Cloud?</a></div>
</div>


Agile workflow solutions for modern teams

We are the one-stop-shop for all your organization's Atlassian needs

Featured Posts

Status of Atlassian Canadian Data Residency

5 Things You Need to Know About Jira Cloud Migration

Case Study: Data Services Migration to Atlassian Cloud

The Atlassian High Velocity: ITSM World Tour is coming!

ScriptRunner for Jira: Migration Evaluation

Insight for Jira: Migration Evaluation

Atlassian Products

Jira Software

Confluence

Jira Service Management

Our Services

Atlassian Services

Custom Development

Our Clients