Completa Studio for Jira
Overview
Completa Studio for Jira is an Atlassian Forge app for Jira Cloud and Jira Service Management, developed by BranchCreation S.L.U.
It solves a common problem: support and operations tickets often ship with a one-line description — a "yes", a "no", a screenshot, and nothing else. Completa adds a field to the create screen that scores the draft against a list of questions a Jira administrator defines, and blocks Create until the draft answers enough of them.
Because it runs on Atlassian Forge, the app itself has no vendor-owned server and no vendor-owned database. It is, however, not a "Runs on Atlassian" app: while someone is typing a description, the draft text is sent to a hosted scoring service, Jev (TypeSafe), at jevtypesafe.org, so it can be compared against the question catalog. See the Privacy Policy and Subprocessors pages linked at the bottom of this page for exactly what that involves.
Key Features
| Feature | Description |
|---|---|
| Admin-owned question catalog | A Jira administrator writes the questions that must be answered, per project, issue type, or JSM request type. |
| Live coverage while typing | After a short pause, Completa scores the draft against the catalog and shows a coverage percentage. |
| Blocks Create below threshold | The ticket cannot be created — or transitioned, if a workflow validator is attached — until coverage reaches the site threshold (default 70%). |
| Writes the native Description | The scored text is copied into Jira's built-in Description field, so agents, search, and reports keep working normally. |
| Flexible enablement | Jira admins can enable Completa for one project, several, or the whole site at once. |
How It Works
- Completa replaces (or sits alongside) Description on the create screen, as a custom field.
- While the reporter types, Completa waits for a 1.2-second pause and at least 40 characters of text, then sends the draft and the configured questions to Jev for scoring. Below 40 characters, coverage is shown as 0% and nothing is sent.
- The field shows "Checking…" only while a scoring request is in flight; the last known score stays on screen while the user keeps typing.
- Until the text on screen matches the text that was actually scored, the field reports itself as not ready, and Jira's own field validation refuses to submit the form. This — not the user waiting for a check to finish — is what enforces the threshold.
- Editing an existing issue works the same way, and each successful score is also synced live into that issue's native Description field, not only after create.
- After the issue is created, an app trigger — and, if attached, a workflow post-function — copy the last scored text into Jira's native Description, so the value is visible to anyone who only looks at Description: search, JQL, exports, other apps.
- On a workflow transition guarded by the Completa validator, the app re-checks coverage and blocks the transition with an error if the draft no longer meets the threshold.
Installation
- Go to Jira Settings → Apps → Find new apps.
- Search for "Completa Studio for Jira".
- Click Get app / Install, and review the requested permissions (see Permissions & Data Handling below).
- Open Apps → Completa Studio as a site administrator.
Enabling a Project
From Apps → Completa Studio, a site administrator can:
- Enable Completa for individual projects, or turn it on for the whole site at once.
- Write and edit the question catalog per project, issue type, or JSM request type.
- Set the coverage threshold that applies across the site (default 70%).
Company-managed projects get the Completa field added to create screens automatically when a project is enabled. Team-managed projects don't expose screen configuration the way company-managed projects do, so an administrator has to add the Completa field to the relevant work type by hand.
On Jira Service Management, remove the native Description field from the portal request form and leave Completa in its place — Jira doesn't let an app hide a native field from a portal on its own, so this step has to be done manually. Completa still writes Description on the created issue, so agents keep seeing it in the agent view.
Permissions & Data Handling
Completa requests the following scopes:
| Scope | Purpose |
|---|---|
read:jira-work / write:jira-work | Read the issue's Description and context, and write the scored text back into Description after create, on transition, and while editing. |
read:jira-user | Identify the signed-in user, for rate limiting and to confirm they administer the site before showing the admin page. |
manage:jira-configuration | Add the Completa field to company-managed create screens when an administrator enables a project. |
read:servicedesk-request / write:servicedesk-request | List JSM request types and attach Completa to portal request forms. |
storage:app | Small operational marks. Question catalogs and settings live in Forge SQL, not here. |
A user-triggered read or write of Description — for example, live sync while editing — only happens after the app confirms, as that signed-in user, that they can browse or edit the issue. Automatic paths with no signed-in user (the create trigger, the workflow post-function, the workflow validator) act as the app itself.
Completa is not a "Runs on Atlassian" app. To score a draft, the Forge backend sends the draft text and the configured questions — nothing else: no issue key, no comments, no attachments — to https://jevtypesafe.org/api/v1/decide. See Completa Studio for Jira - Subprocessors for the full disclosure, and Completa Studio for Jira - Privacy Policy for the legal text.
Scoring requires an active Marketplace license (including a trial) on the site; without one, Completa does not call Jev.
Data Retention
- Question catalogs, project enablement, and the site threshold remain in Forge SQL until an administrator changes them or the app is uninstalled.
- Completa field values (text, coverage, ready flag) live on the Jira custom field and follow normal Jira retention; native Description, once copied, stays in Jira like any other field.
- Uninstalling the app deletes its Forge SQL data for that installation, but does not delete Jira issues or their Description.
Uninstalling the App
- Go to Jira Settings → Apps → Manage apps.
- Find Completa Studio for Jira.
- Click Uninstall.
- The Completa custom fields are removed from your screens after Atlassian's standard retention period. Native Description, already copied, is unaffected.
Troubleshooting
- Coverage never reaches the threshold / field stays not ready: check that the draft actually addresses every configured question; below 40 characters, coverage is always 0%.
- Field doesn't appear on a team-managed work type: add it to the work type by hand — Completa cannot do this automatically on team-managed projects.
- JSM portal still shows a native Description box: remove Description from that request type's portal form; Completa cannot hide it for you.
- Scoring stopped working after install: confirm the site has an active license — Completa does not call Jev without one.
Support & Contact
- Vendor: BranchCreation S.L.U.
- Website: branchcreation.com
- Support email: support@branchcreation.com
For end users with questions or data requests, contact your Jira site administrator first; administrators can disable a project, edit the question catalog, uninstall the app, or use Jira/Atlassian's built-in data-subject tools.