You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 168 Next »

You're reading an article from PHE's web content knowledge base - the best place to find answers to your content questions.

To browse more useful articles, visit our home page.


In This Article



The process of getting new content published



All new content must go through the above process. You must ensure:



Once content is ready for upload, you will need to let us know using the JIRA Service Desk.


Due to the recent system update, only registered JIRA users are now able to use all features of the JIRA service desk.


Register for a JIRA account


If you do not have a JIRA account, you will need to register.


Please enter your PHE email address, password, and your full name i.e. 'John Smith'.



You will then receive a confirmation email with your details.


Once you are all set up and registered, please access the Service Desk with your username and password.


If you have any problems with JIRA, please refer to the JIRA & Agile Knowledge Base for support.

Submitting a new ticket on JIRA Service Desk


Please visit the Service Desk and select one of the following options:


  • submit 2i
  • update content
  • request new content
  • ask a question
  • request GovDelivery support


What should be included in the form


At a minimum, the content team will need to know:

  • details of the content that needs to be published
  • the intended format - publication, press release
  • the date the content needs to be published, or the embargo date


Please remember to include details of:

  • who will be using the content, and the reason they need access
  • the lead point of contact for the content
  • relevant links, including the existing location of the content (please include a web link, or URL)

Example of a completed request form



What to do after you have submitted your ticket


Once you have submitted your ticket, you can continue to use Service Desk for communication about the job.


Please keep all correspondence in the 'comments' on the ticket, and do not switch to email.

What to do before your content is published


Before your content is published, please ensure:

  • you have reviewed the final content
  • the relevant press officer has been notified that the content is being published
  • you have secured sign-off from your manager, or the subject lead

After your content is published

The team will:

  • notify you that the content has been published, or scheduled
  • answer any questions you may have
  • close the ticket 


The ticket can be re-opened if there are any small changes to be made, i.e. minor spelling or grammar amends.


However if you have more substantive changes, such as making significant changes to text or images, or changing important dates or contact details, please open a new ticket.

Time delays when publishing via Whitehall Publisher



The Government Digital Service (GDS) has advised that Whitehall Publisher can sometimes experience delays of up to 30 minutes when adding new content to the GOV.UK live site.


Please try refreshing your browser if content has been published and it is not currently displaying. You can also clear your cache.


Learn more




We hope this article was useful.

To share this article with a colleague, please send them this link: https://confluence.collab.test-and-trace.nhs.uk/x/aYHrHg

You can also return to the home page to browse more articles on knowledge base.

  • No labels