JSM buyer shortlist
10 Jira Service Management Cloud Apps by Use Case
Compare 10 Jira Service Management Cloud apps by the problem they solve, native alternatives and evaluation questions before choosing your next app.
In short
Start with the service problem, then evaluate the app. This shortlist pairs ten JSM Cloud apps with distinct needs and questions to test before purchase.
In this guide
The best Jira Service Management app for your team is the one that solves a specific gap in your service workflow. Start with what JSM already provides, identify the missing behavior, and test an app against that requirement. Adding more apps without an agreed use case makes both administration and purchasing harder.
This guide selects ten apps for ten different JSM Cloud needs. Their order is not a score or ranking. Some improve intake; others support collaboration, reporting or prioritization. Several can be useful together, but inclusion here does not certify compatibility between them.
Publisher disclosure: We build Wezy, which appears in this guide. We reviewed official Marketplace listings and publisher documentation for the other apps; we have not independently benchmarked or deployed all ten. Capabilities were checked on 23 October 2026. Verify current editions, prices, permissions and compatibility before installing.
Start with the native JSM baseline
JSM already includes request types, conditional Forms, queues, SLAs, customer satisfaction surveys, automation and service channels. An app should address a requirement beyond the native setup you can reasonably maintain. Atlassian’s settings overview is a useful starting point.
Before shopping, write one sentence: “When this happens, this person needs to do this, and our current configuration cannot support it.” For example, “Our portal customers need to express demand for an existing feature request without receiving Jira application access.” That is a more actionable requirement than “We need better customer engagement.”
A quick shortlist by problem
| Your main need | App to evaluate | First question |
|---|---|---|
| Customer voting and organization demand | Wezy | Should demand stay on existing JSM requests? |
| Branded service navigation | Refined Sites for JSM | What is missing from our native help center? |
| More structured request forms | Extension for JSM | Which field behavior cannot native Forms cover? |
| Customer edits after submission | Actions for JSM | Which edits and transitions should customers control? |
| A queue spanning projects | Queues for Jira & JSM | Which teams need one operating view? |
| Additional SLA/OLA rules | Time to SLA | Which contract condition requires an app? |
| External customer or asset data | Elements Connect | Which system owns the authoritative data? |
| Teams and Outlook collaboration | Microsoft 365 for Jira & JSM | Which communication context must stay with a ticket? |
| Reports available to customers | view26 | Who should see which report? |
| Expanded satisfaction surveys | Advanced CSAT Survey | What is missing from native CSAT? |
1. Wezy: customer voting on accessible JSM requests
Wezy fits teams that want customers to support selected requests from their existing JSM portal. Agents enroll requests; signed-in customers add or withdraw a vote and can optionally represent an eligible organization. Agents compare votes, represented organizations, recent demand and a demand score.
The supported scope is company-managed JSM Cloud projects. Wezy does not create anonymous voting or a public catalogue of every request. Enrollment does not change JSM sharing. Standard provides a fixed score; Advanced adds organization segments, weights and configurable scoring with a preview and explicit activation. See the official product guide.
Evaluate: can your pilot customer access the intended request, vote once, withdraw, and appear correctly in the agent’s demand view? If your problem is request-level customer demand, evaluate Wezy on Marketplace.
2. Refined Sites for JSM: branded service journeys
Refined builds branded JSM support sites with navigation, layouts and content organized for different audiences. Its Cloud listing describes service portals for IT, HR and external support, alongside site analytics and governance features. Official listing.
Evaluate: give a customer a realistic task, such as finding the right service and submitting a request. Compare completion paths with your current help center. Check the exact edition and any knowledge-content dependencies. If you also use portal extensions, verify their behavior on your chosen portal experience rather than assuming every extension appears automatically.
3. Extension for JSM: richer request intake
Extension provides dynamic fields, grouped fields and additional information on request views. Its Cloud offering addresses both what customers enter before submission and what they can inspect afterward. Official listing.
Evaluate: reproduce your hardest form, including dependencies and required information. Native JSM Forms already supports conditional logic, so identify the specific field types, grouping or request-view details that justify an app. Test with customer accounts and incomplete data, not only the administrator’s ideal path.
4. Actions for JSM: self-service after submission
Actions focuses on letting customers update submitted requests under configured rules. Its listing describes editable fields, drafts, required transition information and a request-progress timeline. Official listing.
Evaluate: choose one repeat interaction currently handled by agents, such as correcting a delivery detail. Define the permitted audience, fields and statuses, then test whether the customer can make the intended change and whether the team can understand the resulting history. Customer convenience must match your process controls.
5. Queues for Jira & JSM: cross-project triage
This app combines requests from multiple Jira and JSM projects in shared queue structures. Its Cloud listing includes queue groups, filtering and access management. Official listing.
Evaluate: specify which projects a service team must triage together and which users should manage the queues. Native JSM queues already support filters and focused views. A useful pilot should demonstrate a cross-project operating benefit, not merely recreate a queue you already have.
6. Time to SLA: additional commitment rules
Time to SLA supports configurable SLA conditions, calendars, countdowns, notifications and reporting across Jira and JSM. Appfire also describes operational level agreements for internal commitments. Official product page and Cloud listing.
Evaluate: model a real contractual case with working hours, waiting states and an escalation. Compare the result with native JSM SLA configuration. Keep this decision separate from feature-demand ranking: a popular improvement must not displace a critical incident or contractual obligation simply because it has more votes.
7. Elements Connect: external context in Jira fields
Elements Connect brings SQL or REST data into connected Jira fields. Its Cloud listing includes customer, directory and asset-context scenarios for service teams, with field dependencies and display controls. Official listing.
Evaluate: choose one authoritative source and document what should happen if it becomes unavailable. Verify authentication, field context, customer visibility and update behavior. An external-data field is useful only if agents understand its source and freshness. Do not assume it automatically supplies data to another app’s score.
8. Microsoft 365 for Jira & JSM: connected conversations
Yasoon’s integration connects Teams conversations, Outlook emails and meeting context with Jira work and JSM requests. The Cloud listing describes bringing work updates back into Microsoft Teams as well. Official listing.
Evaluate: distinguish “create a request from chat” from the broader requirement to retain email, conversation and meeting context. JSM already offers chat channels. Test your actual communication handoff and review the Microsoft permissions required, rather than selecting an integration solely because your organization uses Teams.
9. view26: service reports for customer audiences
view26 provides configurable dashboards, SLA/CSAT reporting and reports accessible through the customer portal, including organization views. Its feature matrix also describes sharing and export options. Official Cloud feature matrix and publisher documentation.
Evaluate: create a customer-specific report with a named audience and inspect the underlying requests. Decide whether native reports cover the internal need and whether portal sharing adds value. Check edition requirements for historical widgets. We have not verified support for Wezy fields in these widgets.
10. Advanced CSAT Survey: expanded satisfaction feedback
Candylio’s Advanced Customer Satisfaction Survey for Jira adds survey ratings and comments, feedback on tickets and project/global reporting. The Cloud listing describes configurable triggers, email content and multilingual surveys. Official listing.
Evaluate: identify the question your native CSAT process cannot answer, then test the survey’s delivery and reporting. Satisfaction and demand measure different things. A customer can be happy with an agent’s response while still wanting an unresolved feature; a satisfaction rating should not become a substitute vote.
Turn the shortlist into one useful pilot
Pick the most costly workflow gap first. Write acceptance criteria, assign an owner and compare the native solution with one app in a compatible test setting. Include an ordinary agent and customer in the review. Record what passed, what failed and the extra administration required before approving a subscription.
For customer voting, use our buyer’s checklist to turn this shortlist into specific acceptance tests.
Frequently asked questions
Do we need all ten apps?
No. They solve different problems. Start with a named gap and evaluate only the apps relevant to it; native JSM may already cover your requirement.
Are these the ten highest-rated Marketplace apps?
No. This is a use-case shortlist published by Wezy, not a rating-based ranking or an independent benchmark. Check current Marketplace reviews and your own requirements separately.
Can we assume these apps work together?
No. Public Cloud availability does not certify compatibility between apps, portal renderers or custom configurations. Test the actual combination, permissions and editions your team intends to use.
Published by the team behind Wezy Customer Voting. Product capabilities are linked to their official documentation; worked examples are illustrative.
Let customers vote on your JSM portal.
Install Wezy from Atlassian Marketplace, open one request for voting and see the first vote in Jira.