Issue management (Internal Board + Jira / Linear / Notion)
Use Revibu's internal issue board and sync tickets to Jira, Linear, or Notion with one click or via automations.
Revibu includes a built-in Issue Board so your team can turn reviews into tickets instantly - even before connecting any external tool.
Then, if you use Jira, Linear, or Notion, you can connect them and define how internal tickets are delivered to your external backlog.
The Revibu Internal Issue Board
Every review can become a structured internal ticket.
Internal tickets support the same fundamentals your team already uses:
- Status (e.g. To do / In progress / Done)
- Type (BUG / FEATURE / IMPROVEMENT / CHORE)
- Priority (LOW / MEDIUM / HIGH / CRITICAL)
- Assignee
- Labels
- Comments & collaboration
Assignees & collaboration
Assignees are taken from the people you've invited to your workspace/app.
- Any invited teammate can be assigned to a ticket.
- Everyone in the workspace can add comments on tickets.
- Comments keep the context linked to the original review.
Push to external tools
On every internal ticket, you'll find:
- Add to Jira
- Add to Linear
- Add to Notion
These buttons instantly deliver the ticket to your external tool using your delivery settings (see below).
You can also push tickets automatically from Automations.
Connect an external tool (Owner only)
To sync tickets outward, an Owner must connect tools once per workspace.
Go to:
/tools
You'll see the list of available integrations:
- Jira
- Linear
- Notion
Click Connect on the tool you want.
OAuth authorization
Revibu uses OAuth for Jira/Linear/Notion.
During the authorization flow:
- Choose the account / workspace you want to connect.
- Accept requested permissions.
- Return to Revibu.
✅ Once connected, the tool appears as Active inside Revibu.
If you manage multiple apps
If your Revibu workspace contains several apps:
- Connect all relevant projects/databases across all apps during OAuth.
- Tools are shared at the workspace level.
The difference will be handled later per app via delivery mapping (next section).
Configure delivery settings (mapping)
After OAuth, you must define how internal issues map to your external tool.
Go to:
Settings → Issue Sync
(or inside an app → Tickets → Delivery Settings)
You will configure, per app, the delivery mapping:
Step 1 - Select destination
Pick where tickets should be delivered for this app:
- Jira Project
- Linear Team / Project
- Notion Database
This is the key per-app choice.
Even though tools are connected at workspace level, each app can deliver to a different external destination.
Step 2 - Map Statuses
Match Revibu statuses to external statuses.
Example:
| Revibu | External |
|---|---|
| To do | Backlog |
| In progress | In Progress |
| Done | Done |
Step 3 - Map Types
Match Revibu ticket types to external issue types.
Revibu types:
- BUG
- FEATURE
- IMPROVEMENT
- CHORE
Map them to your tool's equivalents.
Step 4 - Map Priorities
Match Revibu priorities:
- LOW
- MEDIUM
- HIGH
- CRITICAL
to your external priority system.
Step 5 - Save delivery settings
Click Save.
Your app is now ready to deliver internal tickets to the selected external destination.
Sending tickets outward
Once delivery is configured, you can send tickets in two ways:
Option A - One click from any internal ticket
Open a ticket → click Add to Jira / Linear / Notion.
Revibu will:
- format the ticket,
- apply your mappings,
- publish to the chosen destination.
Option B - Automatically via Automations
In Automations, add an Issue Action:
- enable Jira / Linear / Notion
- set priority / labels
- optional note
Tickets will be created automatically whenever reviews match your automation rules.
Troubleshooting
I don't see my Jira/Linear/Notion destination
- Make sure the Owner connected the tool in /tools.
- Verify the OAuth account has access to the project/database.
Tickets are created with wrong status/type/priority
- Reopen Delivery Settings.
- Double-check all mappings.
Multiple apps deliver to the same project
- That's OK.
- Just select the same destination per app if you want a shared backlog.
You're done ✅
You now have:
- An internal board to capture issues instantly,
- External delivery to Jira/Linear/Notion,
- One-click or fully automated syncing.
Next:
- Set up Alerts
- Launch Automations