ForgeboardGuide
/
Sign in

Sprint retrospectives

Write down what went well and what did not, and turn the agreed actions into issues.

Board → sprint actions → Retrospective

Each sprint can have one retrospective: what went well, what didn't, and the actions the team agreed on. Any action can become a real issue, so it gets tracked like the rest of the work instead of being forgotten.

Open a retrospective

  1. Open the board (Active sprint in the sidebar, or a project's Board tab).
  2. Pick the sprint in the sprint menu. It can be open or completed.
  3. Choose the ... button next to the sprint menu, then Retrospective.

A sprint nobody has written a retrospective for opens on an empty form. The footer shows who started it.

Write it

  • What went well and What didn't: free text, up to 5,000 characters each.
  • Action items: choose Add an action for each one, up to 50, each up to 500 characters. Every action must be different.

Choose Save retrospective. Empty action lines are dropped when you save.

Turn an action into an issue

  1. Save the retrospective first. An action has to be saved before it can become an issue.
  2. Choose Make an issue next to the action.

This creates a task in the sprint's project. Its title is the action's text and its description says which sprint's retrospective it came from. It is created like any other issue: it gets the project's default status and your assignment rules. It is not put into a sprint, so it lands in the backlog. The action then shows the new issue's key as a link.

An action can only become an issue once. If you edit other lines and save again, actions that already became issues keep their link, as long as their own text is unchanged.

Who can do what

  • Anyone who can see sprints can read a retrospective.
  • Saving one needs permission to update sprints, which Owners and Admins have by default.
  • Make an issue needs permission to create issues.

Related