The Jira issue stays the Jira issue

The issue stays the issue

After you start a trial, connect Jira from Account → Integrations. IbisFlow does not become a second backlog. The ticket you open is still the Jira issue. This page does not start Atlassian OAuth.

1. A thin issue will hurt in refinement

   If the ticket 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 Jira issue

   You add the questions and the product context on the connected issue. You save back to the same ticket — not a copy that only lives in IbisFlow. You pick the Jira site from Account → Integrations. The Forge app does not create that connection for you.

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 Jira. The issue you sized is the issue the team will build.

Where to find the listing

The Atlassian Marketplace listing is Free. IbisFlow itself is a separate trial or plan on ibisflow.com. If you opened this from Jira, go back to the Forge app to connect the site.