Page History

Summary of the change

Currently there are 19 status options in the PHE instance and 13 in T&T to indicate the priority of a service desk ticket, backlog item or risk. Each of these priority field options is also indicated by an icon.

These options will be simplified to a P1 (highest priority) to P5 (lowest priority) with accompanying icons.

Why the change?

As part of our continued work to consolidate our technical infrastructure, Jira and Confluence tools will soon move to the Cloud. This technical consolidation is a key part of our strategy to meet budget challenge but is also a great opportunity to simplify and standardise how we work in some areas.

The functionality in the Cloud does not support the multiple priority field options we have available today, so we are making the move to simplify how we use this field. In doing so, we will also see benefit in having clearer parameters for priority decision making, onboarding new team members and clearer data sets for reporting.

ALERT TO IMPACTED USERS

This change to priority field options may seem small, but some teams will need to consider any downstream impacts.

There may need to be modifications to reports driven by priority fields. Please consider this and contact us if you need help in reconfiguring.

You can view how the current options and icons map to the new in the table opposite

Get Involved!

If you have any concerns or questions about this change, or would like to volunteer for User Acceptance Testing (UAT), get in touch here

You can also come along to one of our drop-in sessions - every Thursday at 12:00

Summary of the change

Before the PHE, NTBS and Halo Confluence data can be consolidated onto the single UKHSA Cloud platform, there are a several data conflicts that need to be fixed.

In Jira, these conflicts occur where there are duplicate Project Keys (the unique identifier for the project). 

What does this mean?

The following items will be fixed as part of the fix process and will be tested as part of UAT:

• Filters that are using the project keys
• Agile boards filters, or any swimlanes, sub-queries or quick filters on those boards which have a reference to project key
• Dashboards gadgets that are using filters with reference to project keys
• Automations
• Scriptrunner scripts
• Jira Service Management queues and SLAs
• Links to Confluence

ALERT TO IMPACTED USERS

Please consider the following if you use any of the Jira projects listed opposite:

• Do you use any REST APIs which include the Project Key? If so, these will need to be updated manually
• Do you use any hard coded links to the Spaces that we are changing (e.g. URLs in the page content or comments)? If so, these will need to be updated manually
• If you use the Jira Issue macro in Confluence you will experience a delay in your custom user macros being updated. This will be fixed but you will need to allow some time for the cache to be refreshed

Get Involved!

If you have any concerns or questions about this change, or would like to volunteer for User Acceptance Testing (UAT), get in touch here

You can also come along to one of our drop-in sessions - every Thursday at 12:00

Which Confluence Spaces are impacted?

The Spaces that are required to undergo a change in Space Key are listed below.