When we first launched the Stomio × Jira integration, our goal was to make it simple for teams to push tickets from Stomio to Jira and keep both tools in sync. The configuration was managed at the workspace level, allowing admins to define a single mapping for all betas within the same workspace.
This approach kept things consistent and easy to manage — especially for smaller teams.
However, as our customers grew and we started working with larger enterprise workspaces, we noticed this structure didn’t always fit. Each beta often had its own process, workflow, and Jira setup. The single workspace-level configuration wasn’t flexible enough to handle that.
With this update, Jira configuration is now available at the beta level.
Each beta manager can configure how tickets are pushed to Jira — including ticket type and status — directly from their beta settings.
This provides more flexibility and autonomy for teams managing multiple betas within the same workspace.
To make the integration more stable and easier to maintain, we also deprecated a few features that were rarely used or caused confusion:
These changes simplify the setup and reduce potential errors when pushing tickets.
In addition to the per-beta configuration, access control has changed.
Previously, only workspace admins could manage Jira mapping. Now, beta managers can configure their own Jira settings — no admin involvement required.
This update gives teams faster control and reduces dependency on workspace-level configurations.
We’ll continue improving the Jira integration to make setup more flexible while keeping it simple and reliable.
If your workspace already uses Jira, you’ll find the new per-beta configuration available today.
Got a question or suggestion? Reach out to us: hello@stomio.io
Stomio has earned its reputation as a leading platform for gathering user feedback across...
