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
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?
- There will be a difference to how fields appear
- There will be a change to how lists are updated - Only JSM licensed users will be able to update the data sources.
- 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
Jira Detailed Changes
| What is changing | Why the Change | What does it mean | Who 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. In PHE 1 fragment can't be implemented so this may be a minor user interface change. |
|
| 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. |
|
| Custom Charts for Jira | Is 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. |
|
| JSU Automation Suite for Jira Workflows | Differences between Server and cloud. | There are some feature differences and limitations in the cloud, the main 4 of these are:
|
|
| Xray | There 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:
The following libraries and settings will not be migrated to cloud:
|
|
| Queue Collapse for JIRA Service Desk | There 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. |
|
| Automation for Jira | Differences 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. |
|
| Easy Agile TeamRhythm for JIRA | Difference between server and cloud. | Some feature differences such as:
Users need to be on the most recent version before migration. |
|
| eazyBI Reports and Charts for Jira | The 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.
|
|
| Slack for Jira Server | This 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. |
|
| Structure - Flexible Jira Project Management | Halo 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. |
|
| Structure.Gantt | Halo 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. |
|
| Advanced Roadmaps | Not all data will be migrated to the cloud site. | The following aren't going to be migrated:
Users need to ensure they have the correct version pre-migration. |
|
| Insight | Unlicensed for PHE, cloud feature differences if needed. | Some feature differences, reduced availability or import data types, integrations, rest APIs and objects schema templates. |
|
| Canned Responses | Not Available in Cloud. | Not available in cloud, need to either use a paid add-on alternative or automation. Feature may be a replacement. |
|
| 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. |
|
| Configuration Manager for Jira SPI Bundle | No impact to Halo | Built into Configuration manager for Jira. Users need to download and use the Configuration Manager Cloud Migration Tool application from Atlassian marketplace. |
|
| Easy Agile Programs for Jira | No impact | No feature difference but need to follow migration path using JCMA or Jira site import. |
|
| 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. Workflows using groovy scripts will be replaced during migration. Status or field IDs will need to be adjusted manually. |
|
| Tempo Timesheets | Feature differences between server and cloud. | Some feature differences:
|
|
| Email This Issue Server | Feature 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. |
|
| Smart Checklist | Jira 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 |
|
| Elements Connect | Manual 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. |
|
| 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. |
|
| PII Protection for Jira | License is expired. | Unlicensed app in jira server means it won't be migrated. |
|
| Extended Schemes for JIRA | No migration path is available. | No migration or alternative. All priorities and resolutions will be available as global context in Cloud, there is not separation per project. |
|
| User Management for JIRA | No 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. |
|
| Easy Email Attachments for Service Desk | No 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. |
|
Jira Integrations Changes
| What is changing | Why the Change | What does it mean | Who does it impact |
| Crowd - Department of Health & Social Care Crowd server(Primary) | Replaced by Atlassian SSO | Crowd will no longer be needed to use SSO. Atlassian will provide SSO instead, users will be prompted through Atlassian. |
|
| Department of Health & Social Care Crowd server - 2 | Replaced by Atlassian SSO | Crowd will no longer be needed to use SSO. Atlassian will provide SSO instead, users will be prompted through Atlassian. |
|
| BitBucket | Will not be integrated as the platform is being decommissioned. | No longer needed, functionality available in Jira. |
|
| Bamboo | Will not be integrated as the platform is being decommissioned. | No longer needed, functionality available in Jira. |
|
| Slack for Jira | Site Admins will need to recreate all integrations during migration. | Some work for Admins during migration but should work as normal post migration. |
|
| Github - test and trace | Migration needed into the cloud. | There will be some migration and testing by Admins but should work as normal post migration. |
|
| PowerBI | Hasn'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. |
|
| SN WebHook Listener - Issue commented | The integration is only with HSOP project which is off-loading at 19th of June, so no need to create the integration with Cloud. | Will not be migrated, as will be no longer needed. |
|
| AzureDevOps | Migration to Cloud. | No impact other than some migration work by Admins |
|
| JSM Incoming Mailboxes | Not needed as no mailboxes set up. | No integration in Halo instance. 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. |
|
| Ops Genie | The integration to Opsgenie is pointing to COVID-19 project which is off-loading at 19th of June, so no need to create the integration with Cloud. | Only used in Covid19 project which will be offloaded on 19th June, so wont need to be recreated. |
|
| Confluence | Confluence and Jira both being migrated to cloud. | Some work from Atlassian to fix links, no difference post migration. |
|
| Kahootz | The license has been extended for 12 months but only to use for audit trail, there is no more free space to continue active usage, so Confluence and SharePoint are the recommended storage and sharing spaces to be used. | To be replaced with Confluence and SharePoint as a sharing space. |
|
| Trello | License is not being renewed as it is too expensive and has the same functionality as Jira. | Will not be integrated and the platform will not be decommissioned, teams will use Jira functionality instead. |
|
| QA Portal | Reintegrated with Jira in the cloud | No change post migration. |
|
| Rest API | In Cloud the REST API can be slightly different and the REST Endpoints can change. | Has some differences, users need to adjust rest calls. |
|
| MS Teams | Needs 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 |
|
| Product Plan | License has expired. | Integration is not present in the Cloud |
|
| QAPortal | Will need to be integrated with Jira Cloud. | Integrated fully. |
|