REFERENCETroubleshooting

Forge troubleshooting

The most common Forge problems and how to fix each one, from the most frequent to the rarest.

An issue doesn't show on the board

Cause: the board filters by the active cycle by default, and filters are saved in your browser per team — a forgotten filter keeps hiding issues even after you leave and come back.

  • Switch the Ciclo (Cycle) filter to Todos os ciclos (All cycles) — or Sem ciclo (No cycle), if the issue isn't in any cycle.
  • Clear the Tipo (Type), Responsável (Assignee), Iniciativa (Initiative), and Domain filters, and turn off Minhas issues (My issues).
  • If the issue was archived, switch to the Lista (List) view and filter Status by Arquivado (Archived).

The Nova iniciativa button is disabled

Cause: the team has no domain yet — every initiative requires one. The command palette shows the hint “Crie um domain primeiro” (Create a domain first).

  • Open Domains in the Forge sidebar and click Novo domain (New domain).
  • Create the domain and go back to Initiatives — the Nova iniciativa (New initiative) button becomes enabled.

“Nenhum PR vinculado” (No linked PR) on the issue

Cause: the branch or the PR doesn't reference the issue — the link is automatic only when the branch starts with the iss-N- pattern or the PR description contains closes #N.

  • On the issue's full page, use Copiar nome da branch (Copy branch name) and create the branch with that name.
  • For an already-open PR, add closes #N (with the issue's number) to the description.
  • Confirm that the GitHub integration is connected and the repository is synced.

“Não encontramos o time que iniciou a conexão. Volte ao Forge e tente novamente.” (We couldn't find the team that started the connection. Go back to Forge and try again.)

Cause: the GitHub App installation was finished in another browser, or the site's local data was cleared along the way.

  • Go back to the Forge GitHub page.
  • Click Conectar GitHub (Connect GitHub) and finish the installation in the same browser, without clearing data along the way.

“A assinatura do GitHub não confere com o pedido enviado. Por segurança, reinicie a conexão.” (GitHub's signature doesn't match the request that was sent. For security, restart the connection.)

Cause: the security check on GitHub's return didn't match the original request.

  • Restart the connection from the Forge GitHub page, with Conectar GitHub (Connect GitHub).

I can't edit the cycle's dates

Cause: what can be edited depends on the cycle's state — fields outside the rule appear disabled.

  • Próximo (Upcoming): Objetivo (Goal), Início (Start), and Término (End) — and only in this state can the cycle be removed.
  • Ativo (Active): only Objetivo and Término.
  • Concluído (Completed): only the Objetivo.

The cycle shows no burndown

Cause: the cycle is still Próximo (Upcoming) or has no issues. There is no start action — the cycle becomes Ativo (Active) when its start date arrives.

  • Bring the cycle's Início (Start) forward (possible on Próximo cycles) or wait for the date.
  • Add issues to the cycle with Adicionar issue ao ciclo (Add issue to cycle), on the cycle's Lista (List) tab.

“Você precisa de permissão de gestor (FORGE_MANAGER) para ver este painel.” (You need manager permission to see this panel.)

Cause: the Bloqueios (Impediments) page is restricted to Forge managers and admins.

  • Track your own issues' impediments through the Inbox's Bloqueada (Blocked) section.
  • If your role should be manager, ask a team admin to adjust it in team members.

Repositories don't appear after connecting

Cause: the GitHub App installation doesn't include the expected repositories, or the list hasn't been synced yet.

  • In GitHub, click Gerenciar instalação (Manage installation) and confirm which repositories the app can access.
  • Click Sincronizar repositórios (Sync repositories) and check the “Última sincronização” (Last sync).

Next