GitLab issues stay in GitLab

The issue stays the issue

After you start a trial, connect GitLab from Account → Integrations. IbisFlow does not become a second backlog. The ticket you open is still the GitLab issue. How you authorise — OAuth or a token — is explained on the Alliance page. This page does not start OAuth or ask for a token.

1. A thin issue will hurt in refinement

   If the issue is still a title and a hope, the room will invent the work. Shape it first so ranking and sizing have something real to talk about.

2. Shape it while it is still that GitLab issue

   You add the questions and the product context on the connected issue. You save back to the same issue — not a copy that only lives in IbisFlow. How you authorise is on the Alliance page. The work is still the GitLab issue.

3. Rank it when more than one voice needs a say

   Stakeholders can score that same issue. When you publish, the ranking writes back. The slide deck is not the system of record.

4. Size it with the room, then write the number back

   The team votes on the same issue. An accepted estimate writes back to GitLab. The issue you sized is the issue the team will build.

GitLab Alliance

The Alliance page is where we explain how connect works. That page also does not start OAuth.