Here's what Viable Issues can do
Stop juggling fields and tabs. Viable Issues lets you place smart ‘Create Issue’ buttons on any Confluence page, so you can quickly create Jira tickets that follow your rules—and report back in real time.
Explore, learn, connect
-
Marketplace
Automate Jira checklists for Definition of Done, Acceptance Criteria, ToDo lists, and more—smarter than Jira Action Items -
Product advice
Need help deciding which app solution would be perfect for your team? Want to clarify and compare app features with a real person? -
-
-
-
What customers think of
Viable Issues
Stuff you probably want to know
What does Viable Issues actually do?
It lets you drop “Create Issue” buttons anywhere in Confluence. Each button carries your pre-set Jira fields (project, type, labels, etc.), so anyone can raise a fully-routed ticket in one click—without leaving the page. A built-in Page Report lists every issue created from that page and its live status, keeping planning and execution in one place.
How is Viable Issues different from Confluence's built-in "Create Jira issue"?
| Edition | Confluence native | Viable Issues |
|---|---|---|
| Cloud | Quick but ad-hoc
| Preset, reusable & works in both modes
|
| Data Center | Basic macro — summary & description only
| Full field population unlocked
|
Which fields can we pre-set & who can edit a button?
Currently the following fields can be pre-configured:
- Project
- Issue Type
- Labels
- Priority
- Component
- Epic Link
Anyone with space-admin or page-edit rights can place or modify a button. View-only users can still click it (as long as they also have Jira “Create Issue” permission). Coming soon: an option to restrict button editing to admins only.
On our road-map: Adding support for more fields including assignee, custom fields, and more, as well as field-locking so only admins can change a button’s settings.
How do we keep track of the issues we create from a page?
Add the built-in Page Report macro. It lists every issue that originated from that page and shows live status—no JQL filters or hopping to Jira.
Does it work with Confluence templates?
Viable Issues works anywhere in Confluence, including templates (e.g., meeting notes, project space, risk log). Every new page created from that template inherits the button’s field settings—giving you a repeatable workflow without extra setup.
Is it available on Data Center?
Yes—the same Marketplace listing covers Cloud, Server and Data Center.
If you run Jira Server or DC you’ll also install the free Viable Issues Extension add-on. It enables the full field-population features described above.
Is my data secure and compliant?
All data stays inside your Atlassian site. Viable Issues stores its configuration in Confluence and writes tickets to Jira via Atlassian-approved APIs—no external servers or exports. See “Privacy & Security” on our Marketplace listing for details.
How much does Viable Issues cost?
Pricing for Viable Issues is based on the number of users in your Confluence instance. To get an estimation, check out the pricing tab on the Marketplace.
You get a 30-day free trial for Cloud and an evaluation licence for Server/Data Center, both available directly through the Atlassian Marketplace.
