Applications, Plug-ins, Add-Ons and Integrations

There are a significant number of tools available that integrate with Jira and Confluence, offering additional functionality. We don't currently have enough control around these apps and plug-ins meaning we use a great number across the estate, some from suppliers or data centres that do not comply with UKHSA policy. 

As part of the consolidation to Cloud, we will be updating our App and Plug-In offering which will bring the following benefits:

  • Increased financial efficiency across our technology infrastructure
  • Maximise the scope of our agreed technology capabilities
  • Standardise ways of working
  • Enable us to collaborate better between teams.

Browse the sections below to find out whats changing and what this will mean.

Elements Connect CloudElements Connect

What is changing?

We are replacing use of Elements Connect add-on with built in functionality within Jira Service Management, called Assets (Insight).

Why the change?

The Cloud offering of Jira does not offer the functionality required by the 45 use cases that have been identified. The requirement is to read content from Confluence attachments, parse their values into Jira fields, and change the options for each field dynamically based on the value of other connected fields.


What does the change mean?

  1. There will be a difference to how fields appear
  2. There will be a change to how lists are updated - Only JSM licensed users will be able to update the data sources.
  3. Autocomplete fields will work as select list fields instead

FOR MORE INFORMATION, YOU CAN VIEW THE FULL IMPACT GUIDE BELOW:


Who does this impact?

Colleagues working on the PHE instance of Jira working in the following spaces:

  • ARSAC
  • BOD
  • Culture Collections
  • HIEF - Health Intelligence Enquiries Feedback
  • IHR / GDRR
  • Indictor Production
  • LKIS / HIHI
  • NVAP
  • RTI
  • Science Hub Business Design
  • Science Hub ICT
  • UKAS
  • UKOT
  • Testing (Gary)
  • IPSD - Intranet

Applications, Plug-ins, Add-Ons and Integrations: Impact Maps

 

NOTE: For the best experience please download this deck and view in presentation mode.

Jira: Apps and Plug-ins Detailed Changes


What is changingWhy the ChangeWhat does it meanWho does it impact?
Adaptavist ScriptRunner for Jira

Differences between server and cloud.

(Atlassian doesn't allow add-ons to inject Javascript or other frontend resources into the page.)

Fragments which are used to personalise the user experience can't be implemented.

There are some feature differences and limitations as some add-ons are not allowed, this means admins will need to manually rewrite some scripts as a workaround and during migration.

Some alternatives or replacements to the current API approach may be needed.

In PHE 1 fragment can't be implemented so this may be a minor user interface change.

  • Users
  • Site Admins
Configuration Manager for Jira (CMJ)

Admins have said they’re not using it, so it is not being migrated, On the PHE side the License has expired.

On jira cloud there is a similar add on with limited functionality so it is suggested to use this instead. 

Instead users or Admins will need to download Configuration Manager Cloud Migration Tool from Atlassian marketplace.

For admins the Atlassian tool can't migrate some data so JCMA will need to be used instead.

  • Users
  • Site Admins
Custom Charts for JiraIs being manually migrated and charts will need to be recreated in cloud.The manual migration means admins will have to manually recreate any charts into the cloud. In terms of functionality users can search for issues in the same way.
  • Users
JSU Automation Suite for Jira WorkflowsDifferences between Server and cloud.

There are  some feature differences and limitations in the cloud, the main 4 of these are:

  • JQL Condition is not available
  • Location, Location Select, and Directions custom fields are not available
  • Users will not be able to store variables per project which then can be used in workflow post functions.
  • Preconditions are no longer separate post functions; they are now part of the post function.
  • Users
XrayThere are a few subtle differences between Server and Cloud due to Jira's architecture and the Product's Age.

Some subtle feature differences which will lead to a change in the user interface. Key Limitations include:

  • Issue History and Test Run Activity - The language, phrases and markups may differ.
  • Migration drift not supported - All linked data must be migrated together so data integrity can be guaranteed on the cloud.
  • Document Generator - Templates must be revised once migrated.

The following libraries and settings will not be migrated to cloud:

  • Automated Step Library
  • Cucumber settings
  • Gadget Configuration 
  • Archived Issues
  • Users
  • Site Admins
Queue Collapse for JIRA Service DeskThere is no alternative for the feature in Cloud due to Atlassian's design.While the icon to collapse will be there, queues won't be collapsible.
  • Users
Automation for JiraDifferences between server and cloud.

Some feature differences.

For admins if importing rule owners, Id's need manually changed after the import. Some rules need reconfigured, imported rules need to be reviewed manually after the migration to check the mapping is correct.

Admins need to check for global automations in Halo and change permissions in them.

  • Users
  • Site Admins
Easy Agile TeamRhythm for JIRADifference between server and cloud.

Some feature differences such as:

  • Unable  to display epic statistics on the story map
  • Some issues in issue editing
  • Some issues regarding cards.

Users need to be on the most recent version before migration. 

  • Users
eazyBI Reports and Charts for JiraThe common functionality is the same for all hosting environments but there are some technical limitations to the cloud.

Functionality is the same but there are some technical limitations. 

  • Gadgets on dashboards wont be available, current dashboards using gadgets will be migrated manually.
  • There may be some issues in integrations with advanced roadmaps and X ray during the migration.
  • Users will not be able to use dashboards with gadgets before the migration and there will be a transition window when these reports aren't available.
  • Users
  • Site Admins
Slack for Jira ServerThis specific app is not available in Cloud, however users can use the free Cloud alternative - Jira Cloud for Slack. Replaced with Jira cloud for Slack, users will need to install the Jira cloud app then follow the guide to integrate. 
  • Users
Structure.GanttHalo will not use Structure in Cloud as the data residency is in Russia.Advanced Roadmaps is the recommended replacement, users should recreate Gants and PM work on Advanced roadmaps or Big Picture Plug in. 
  • Users
Advanced RoadmapsNot all data will be migrated to the cloud site.The following aren't going to be migrated:
  • Classic plans
  • Plans with Issue Sources as private filters
  • Unsaved Scenario Date
  • Saved Views
  • User defined custom field types:
    • Parent Link
    • Team
    • Target start
    • Target end

Users need to ensure they have the correct version pre-migration. 
  • Users
InsightUnlicensed for PHE, cloud feature differences if needed.Some feature differences, reduced availability or import data types, integrations, rest APIs and objects schema templates.
  • Users
Canned ResponsesNot Available in Cloud.Not available in cloud, need to either use a paid add-on alternative or automation. Feature may be a replacement.
  • Users
Integrity Check for Jira (Configuration Manager)

This is part of Configuration Manager now.

Built into Configuration manager for Jira. Users need to download and use the Configuration Manager Cloud Migration Tool application from Atlassian marketplace. 
  • Users
Configuration Manager for Jira SPI BundleNo impact to HaloBuilt into Configuration manager for Jira. Users need to download and use the Configuration Manager Cloud Migration Tool application from Atlassian marketplace.
  • Users
Jira Misc Workflow Extensions (JMWE)The main difference for JMWE Cloud and JMWE Server/Data Center is that Server uses Groovy scripting whereas Cloud uses a combination of Nunjucks and Jira expressions.

No difference to end users.

Shared actions, Event-based actions, and Scheduled actions are not  migrated and must be recreated manually.
Scripts will need to be rewritten differently to prevent errors.
Some change to ways of working including error handling post transaction.

Workflows using groovy scripts will be replaced during migration. Status or field IDs will need to be adjusted manually.

  • Users
  • Site Admins
Tempo TimesheetsFeature differences between server and cloud.

Some feature differences:

  • Log expenses are not available
  • Groups in teams are not supported
  • Logging time of issues might have some limitations
  • PHE
*Email This Issue ServerFeature differences between server and cloud.Some configuration that is outdated will not be migrated. There is an add-on update that will be required before migration. 
  • Users
Smart ChecklistJira Cloud Migration Assistant is supporting  Smart Checklist Migration. Some pre and post-actions need to be performed.Some feature differences such as no customer permission and access for checklists and no "assign checklist items for me" feature
  • Users
*Elements ConnectManual recreation of the configuration is required.

Live text fields are not available in Cloud. All live fields need to be converted to Snapshots, post functions aren't available and the rule action feature is no longer available.
  • Users
  • Site Admins
Microsoft Teams for Jira Server The migration actions include the installation of the Cloud compatible app in the Jira Cloud site, and follow the documentation to establish the integration in both Teams and Jira side.Teams admin need to establish new connection with cloud based app. No data migration needed.
  • PHE
  • Site Admins
Extended Schemes for JIRA

No migration path is available.

Also no alternative options due to Atlassian architecture limitations.

No migration or alternative.  All priorities and resolutions will be available as global context in Cloud, there is not separation per project.
  • PHE
User Management for JIRANo migration is required. This app will be replaced by Atlassian Access on Cloud.Most management will be done by Azure AD. Atlassian Access will be used for visualisations of access and reports. 
  • Users
Easy Email Attachments for Service DeskNo migration is required.

Also, no alternative is available due to security policies, only links to attachments are available in Cloud.		Transitions and validators used as a workaround, only links to attachments will be available in cloud.
  • Users



Jira: Detailed Integrations Changes

What is changingWhy the ChangeWhat does it meanWho does it impact
Crowd - Department of Health & Social Care Crowd server(Primary)Replaced by Atlassian SSOCrowd will no longer be needed to use SSO. Atlassian will provide SSO instead, users will be prompted through Atlassian.
  • Users
Department of Health & Social Care Crowd server - 2Replaced by Atlassian SSOCrowd will no longer be needed to use SSO. Atlassian will provide SSO instead, users will be prompted through Atlassian.
  • Users
Slack for JiraSite Admins will need to recreate all integrations during migration.Some work for Admins during migration but should work as normal post migration.
  • Site Admins
PowerBIHasn't previously been integrated with Jira and no integrated instance possible.Will not be integrated with Jira, but manual workaround using download of information still in place.
  • Users
AzureDevOpsMigration to Cloud.No impact other than some migration work by Admins
  • Site Admins
JSM Incoming MailboxesTBC

Emails that are set up on specific JSM projects and create tickets based on the incoming emails. Some work being done to see how to connect emails.

  • Users
  • Site Admins
ConfluenceConfluence and Jira both being migrated to cloud.Some work from Atlassian to fix links, no difference post migration.
  • Users
QA PortalReintegrated with Jira in the cloudNo change post migration.
  • Users
  • Site Admins
Rest APIIn Cloud the REST API can be slightly different and the REST Endpoints can change.Has some differences, users need to adjust rest calls.
  • Users
MS TeamsNeeds reintegrated so Jira can send updates to Teams.Will be integrated as normal.  Teams channel owner should generate a new URL and provide it to admins so they can set up the webhooks accordingly
  • Users
  • No labels