Correct what matters
Allow updates to supported request fields instead of making every change a separate conversation.
BUILT FOR JIRA SERVICE MANAGEMENT
Request changes,
without losing
control.
Give people a clearer way to update supported request fields—while keeping permissions and editing rules in place.
Built on Atlassian Forge Jira-aware editing controls
REQUEST EDITING · CONCEPT•••
EDIT REQUEST
Update request details
Only configured fields can be updated
Allowed
Request category
Access request
Preferred date
Choose a date
Illustrative interface — not a real app screenshot
SHURIVO / REQUEST EDITINGWhy controlled editing matters
A BETTER WAY TO HANDLE CHANGES
Information changes.
Your process stays intact.
Requests rarely stand still. Shurivo makes room for supported corrections without turning every update into an unrestricted edit.
WHY SHURIVO
Keep the request moving. Keep the rules.
A practical editing layer for teams that want flexibility without losing the context and controls of Jira Service Management.
Respect permissions
Editing decisions account for authorization, configured rules and the request context.
Stay inside Jira
Permitted request changes are saved back to Jira Service Management, where the work happens.
THE WORKFLOW
A clear path from change to update.
Three straightforward stages make the editing approach easy to understand.
01
Define the boundaries
An administrator configures supported fields and applicable project-level editing rules.
02
Check the context
An attempted edit is evaluated against relevant permissions and request conditions.
03
Update in Jira
Allowed changes are written to the original request, with audit information recorded inside Jira.
CAPABILITIES
Purpose-built for the details.
Focus on the core: configurable boundaries, permission-aware changes and supported field types.
01
Configurable editing controls
Define supported editing options with project-level rules and field configuration.
02
Authorization in context
Consider request status and actor permissions before a supported update proceeds.
03
Practical field support
Work with tested numeric, choice, date, label and checkbox field types.
Documented test coverage
NumberDropdownRadio selectionMulti-selectCheckboxDate / date-timeLabels
TRUST IS PART OF THE PRODUCT
Your requests belong in Jira. So do your updates.
Shurivo runs on Atlassian Forge. Approved request edits are written inside Jira; project configuration uses Forge-hosted storage. Shurivo does not operate an external app runtime server or customer-data database.
Explore the trust centerCOMMON QUESTIONS
Good to know before getting started.
Straight answers about what Shurivo does and where it fits.
What does Shurivo do?
Shurivo provides controlled editing for supported fields on Jira Service Management requests, subject to configuration, permissions and request context.
Can any requester edit any field?
No. Whether an edit is allowed depends on configured field rules, authorization and other applicable request conditions.
Which field types have been tested?
The project records functional tests for number, dropdown, radio selection, multi-select, checkbox, date/date-time and labels. Exact behavior can depend on Jira configuration.
GET TO KNOW SHURIVO
Less friction.
Clearer control.
Explore what Shurivo can do for your Jira Service Management requests.