Many Jira Service Management portals technically give customers visibility. Requests are submitted. Reports are available. Data is reviewed.
And yet — action still happens somewhere else. A customer spots an incorrect priority, notices missing information, or needs to update a field, but the actual change often requires opening the underlying Jira issue. In many cases, that means additional steps, additional permissions, or even an additional Jira license.
For teams managing high volumes of service requests, this creates unnecessary friction. Visibility is useful, but visibility without timely action still leaves support teams doing manual follow-up work.
Advanced Edition for Advanced Portal Reports is designed to close that gap.
Advanced Edition is available as an upgrade for existing Advanced Portal Reports customers. New customers can install Advanced Edition directly from the Atlassian Marketplace and start with the Edition version from the beginning.
It introduces controlled in-line editing directly inside report views, allowing selected portal users to update specific Jira fields without leaving the Jira Service Management customer portal.
To put it simply, users can act on request data right where they already review it — while admins keep full control over what can be changed, by whom, and under which conditions.
What Advanced Edition Adds
Advanced Edition extends Advanced Portal Reports with in-line editing for selected Jira fields inside customer-facing reports. Instead of switching contexts, opening the Jira issue, or asking an agent to make a simple update, authorized users can make allowed changes directly from the report.
The feature currently supports editing of:
- Priority
- Number fields
- Single-select fields
This is especially useful when portal users need to help triage, categorize, or refine requests after they have already been created.
The result is a more practical self-service experience: customers and internal stakeholders do not only see what is happening — they can contribute to keeping the data accurate and actionable.
Control Stays With Admins
Advanced Edition keeps configuration in the hands of Jira and project admins. Once the edition is activated, a new Editable fields section becomes available in the project configuration. From there, admins define:
- Which fields can be edited
- Who is allowed to edit them
- Under which conditions editing is available
This means organizations can introduce in-line editing gradually and safely. A field can be made editable for the right audience, in the right context, without opening unnecessary access across the entire portal.
Jira remains the system of record. Every change is still captured with full audit history, preserving transparency and traceability over every action taken.
In other words, Advanced Edition does not bypass Jira governance. It brings governed Jira actions closer to the people who need them.
Why This Matters for Customer-Facing Teams
In larger service environments, small administrative steps accumulate quickly.
When customers or internal business users cannot update simple request information themselves, support teams become the middle layer for every minor correction. Agents spend time adjusting priorities, updating numeric values, or changing categories instead of focusing on more complex service work.
Controlled in-line editing helps reduce that operational noise.
For customer-facing teams, this can mean:
- Fewer back-and-forth comments for simple request updates
- Faster prioritization of important issues
- More accurate report data
- Less manual work for agents and project admins
- A smoother portal experience for customers and stakeholders
The goal is to make the right updates possible at the right moment, directly from the place where decisions are being made.
What We See in Jira Service Management Environments
In many mature Jira Service Management setups, reporting becomes the main place where business users understand what is happening across requests.
They review priorities. They compare request types. They look at progress, volume, and ownership. But when reports are read-only, any needed change becomes a separate process.
Over time, this creates a familiar pattern: users rely on reports for visibility, while agents remain responsible for keeping the underlying data updated. That separation slows teams down and can make reporting less accurate than it should be.
Advanced Edition addresses this by turning reports into a more active part of the service process — without sacrificing control, permissions, or auditability.
What to Do If You Are Already Using Advanced Portal Reports
Action required: Update Advanced Portal Reports to the latest version. This applies to all customers — whether or not you plan to activate Advanced Edition right away.
Why:
- Advanced Edition features are only available on the latest version
- Standard Edition updates and compatibility improvements also require it
- Staying on an older version means missing future fixes for both editions
Already on the latest version? Review your portal workflows and identify where controlled inline editing could save your team time — then activate Advanced Edition from project configuration.
New customers can install Advanced Edition directly from the Atlassian Marketplace and start with the Edition version from the beginning.
Turning Visibility Into Action
Advanced Portal Reports has always focused on giving customers and stakeholders clearer access to service request data.
Advanced Edition builds on that foundation by making selected report data actionable. It helps teams move from “we can see the problem” to “we can update what matters” — directly in the portal, with the right controls in place.
For organizations handling high request volumes, this can reduce administrative overhead, improve data quality, and create a more efficient service experience for everyone involved.
Want to See Advanced Edition in Action?
We can walk you through how controlled in-line editing works, where it fits best, and how to configure it safely for your Jira Service Management portal.