Administration
Install
- Jira > Settings > Apps > Explore apps, search for “Design Reviews & Baselines”, Install. The free trial lasts 30 days; the app is free up to 10 users.
- Open a project: the Reviews & configuration entry appears in the project sidebar (Apps section). In a project created just before, it can take 10 to 20 minutes to appear: reload the page. The Design reviews panel is available on issues from the issue's View app actions menu.
- Settings > Apps > Design Reviews & Baselines opens the site settings (Jira admins).
Nothing else to install: the app runs on Atlassian Forge, inside Atlassian's infrastructure.
Site settings
| Setting | Effect |
|---|---|
| Review types offered | Types offered when creating a review (at least one). |
| Default exit criteria | Copied into each new review, which can then adjust them. |
| Who can create a review | Anyone who can browse the project, or project admins only. |
| CSV export separator | By language (semicolon in French, comma in English), or forced. |
In each project, the Configuration > Managers tab lets a project admin appoint configuration managers.
Requested permissions (Forge scopes)
| Scope | Why |
|---|---|
read:jira-work |
Read projects, issues and your permissions on the project (Browse, Administer). |
write:jira-work |
Create, on your request, the follow-up issue for an action decided in review. |
read:jira-user |
Show participants' names and avatars. |
storage:app |
Store reviews, RIDs, items, baselines and the audit log in your site's Forge storage. |
Calls to Jira are made as the user: the app only sees what that person sees. The agent tools have one fallback, described below.
Rovo agent and MCP server
- Rovo agent. Requires Rovo on your site. The agent Design Review Assistant then appears in the agent list of Rovo chat. There is nothing to configure in the app.
- Whose permissions. Each tool runs for the person who talks to the agent. The app first asks Jira who the user is, with a call made as that user; Jira then enforces its own permissions on every later call. If the platform gives an agent action no user session, the app uses the account that Forge declares for the invocation, calls Jira as the app and checks that account's permissions itself before returning anything: Browse on the project, visibility of the issue, Browse users and groups. If that check cannot be made, nothing is returned. A call with no user at all, such as an unattended automation, gets no data.
- One write. Ten tools only read. One,
raise-rid, raises a RID in the user's name, after the agent has shown the draft and the user has confirmed. It follows the rules of the app and is refused while the licence is inactive. - MCP server. The app declares an MCP server named “Design Reviews & Baselines” with the same eleven tools, for agents built in Rovo Studio. The tools are also exposed to agents built in Rovo Studio through the
rovo:mcpmodule. External MCP clients are off by default and are enabled by a site admin in Atlassian Administration. When an external client is connected, the tool results it asks for (review and RID content the user can read) are sent to that client. Leave it off if review data must stay inside Atlassian.
Sample program
In a project that has no review and no configuration item yet, a project admin sees Load the ALTAIR sample program under the empty review list. It fills the project with a fictional micro-satellite program: 4 reviews in different phases, 22 RIDs, 9 configuration items, a baseline, 6 changes and 2 change boards, plus 4 sample issues in the Jira project when its required fields allow it. The person who loads it holds every role; reviewers are fictional names in the Originator field. Loading takes a minute or two and can be resumed if the page is closed. When it ends, the list may take a few seconds to show the reviews (the page refreshes itself); if it stays empty, reload the page.
If you have just created the project and the button is missing, wait a few minutes and reload the page: Jira can take about 4 minutes to report the project administrator permission to apps (and 10 to 20 minutes before the app page appears in a new project), and the sample is offered only to a project admin.
Use a trial project: reviews, RIDs and audit log entries cannot be deleted afterwards. Uninstalling the app deletes all of its data.
Data
All app data lives in the Forge storage of your Atlassian site. The app has no third-party server and data does not leave Atlassian's infrastructure, unless a site admin opens the MCP tools to an external client (see above). Backup: export RIDs (CSV), minutes (PDF), status accounting (CSV, PDF) and change board records (PDF). On uninstall, Atlassian deletes the app's data under its Forge retention rules.
Licence
If the licence expires or is not renewed, the app becomes read-only: everything stays readable and exportable, nothing can be changed. A Jira admin reactivates it from Settings > Apps > Manage apps.
Support
“Support” tab of the Marketplace listing, or support@consignestudio.fr. First answer within 1 to 3 business days depending on severity (see the support policy).