Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Section
Table of Contents

Raise a request

Go to the service desk portal - https://jira.collab.test-and-trace.nhs.uk/servicedesk/customer/portal/12

At the bottom of the page select one of the two options depending on whether you have devolved author access to Whitehall publisher or not.

If you do, select the second option, if you do not, select the top one.

Image Added

Standard Gateway Submission

Complete as many of the fields as possible. 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 also 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

When you submit a brief to the content team, it is important that we are provided with a complete brief that covers all the important information. This ensures that we can progress your brief efficiently.

Before you submit a new request, please run through the checklist below.

Tip
  • We will need as much notice as possible before publishing new content, especially if it needs to go out at a certain time.

...

Submit a content request

To submit a content request you will need a Jira Service Desk account. If you do not have one you will need to register a new account.

Once you have an account, please choose one of these four options:

Explain the request

  • What kind of content needs to be published - is it a publication, a consultation, a news item or a set of statistics.
  • What format it is - for example, a publication, consultation, news item or press release
  • Who will be using this content
  • Why do they need access to the content, and how will it help them
  • When does the content need to be published
  • Where should the content be published when it has been signed off
  • a title - it should be 65 characters or less
  • a summary of the new content in 140 characters or less (must not repeat the title)

Add important links and contacts

  • Lead point of contact for this content
  • Required publication date
  • Embargo time and date, if this is applicable
  • Existing location of the content (please include the a web link, or URL)
  • Intended location of the new content (please include the URL)

Review and secure approvals

Then click Create.

Image Added

This will create a new ticket in the Service Desk.

The ticket will be marked as Open.

What to do after you have submitted your ticket

Once you have submitted your ticket, you will receive email notifications as the work progresses through key stages, for example when:

  • the ticket is assigned a number
  • is assigned to a member of the Publishing team
  • moves through the process from Backlog, to Assigned, to In Progress and so on.

Correspondence on the ticket

There is sometimes email correspondence or phone calls about aspects of a ticket.

It is important that notes of any decisions relevant to the ticket are added to it via Comments.

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
  • Review the final content
  • Give your approval via the JIRA comments section
  • Notify the relevant press officer that the content is being published
  • Ensure you have secured sign-off from your manager, or the subject lead

...

borderColor#2F4F4F
bgColor#FAFEFF

Useful resources

Types of content on GOV.UK

Content by Label
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@2265b8
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("content","request","brief") and type = "page" and space = "IPSD"
labelsbrief request content

...

hiddentrue

...