Check your junk or spam folder first. If the invite isn't there, ask your Manager to resend it from Jira. You won't be able to log in until the invite has been accepted.

Your role probably hasn't been assigned yet. Boards are only visible once your access level is active. Contact your Manager or PIIT - they can confirm your role and which boards you should see.

Editors can create, update, and move items on the board. Viewers can read and comment but cannot create or move items. Most pilot users are Editors. Your role is assigned by PIIT.

An epic is the parent - the big piece of work (e.g. a briefing cycle, a factsheet). Tasks sit under the epic and represent distinct pieces of work, each with a single owner. Subtasks sit under a task and break it down further - used when multiple people need to track their own steps independently.

Everything. Jira is the team's system of record for all communication and engagement work - including recurring coordination like monthly meetings, short turnaround items, and review tasks. If it requires coordination or has an owner, it belongs on the board.

Complete the task’s required fields - Name, Description, Assignee, Reporter, Alliance and a URL, plus a Due date where known - and make sure the correct Component is set so the item appears on the right board. This keeps the board readable and actionable for everyone.

Sequential review: one subtask moves between reviewers in order - when the first reviewer is done, they reassign it to the next with a comment. Use this when reviewers need to build on each other's feedback.

Parallel review: each reviewer gets their own subtask and they work simultaneously. Use this when reviewers are independent. The Stakeholder Meeting and Tottenham Factsheet walkthroughs in Layer 2 have both as worked examples.

No - each task has one Assignee who is accountable for it. If multiple people need to track their own work, use subtasks and assign each subtask to its owner.

The Reporter is the person accountable for the task - they are notified automatically when the status or Assignee changes. Jira defaults this to whoever creates the task. If you're setting up a task on behalf of someone else, update the Reporter to the right person.

The internal team member retains ownership and stays as the Assignee. Use the comment field to log correspondence, approvals, and outcomes from external parties. External parties do not have board access unless PIIT provisions it.

Within 5 working days of any change. Any item inactive for 30 days or more must be reviewed and either updated or closed. Your Manager is accountable for board health and will follow up on stale items at the monthly governance review.

Review it. If the work is still live, update the status and add a comment logging where things are at. If the work is no longer proceeding, move it to Cancelled - do not delete it. If you're unsure, raise it with your Manager.

Done means the work was completed. Cancelled means it was decided not to proceed. Both close the item on the board. Do not delete items - deletion removes the record permanently and is only for correcting errors.

Start with your Manager - they are accountable for board health and can action or escalate most issues. For access problems, configuration issues, or anything that needs platform-level action, escalate to PIIT.