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