Jira Service Management vs Sortly

Jira Service Management

The most capable ITSM platform a district can actually afford — Atlassian gives K-12 a 50% academic discount — but self-hosting has closed to new customers, and its CMDB is an empty box you have to model yourself.

Where Jira Service Management is strong

• ● The deepest ITIL process set of anything on this page: incident, problem, change, and request management, service catalog, approvals, SLAs, on-call schedules and alert routing, and deployment gating tied to CI/CD.
• ● A real academic discount that names K-12 districts and boards of education — 50% off Jira Service Management on Cloud, 75% off Confluence, and Atlassian Guard free.
• ● The Free plan is genuinely usable for a small shop: three agents, unlimited customers, and an embedded knowledge base included, with no trial clock.
• ● Assets is included from Standard upward with 5,000 objects, rising to 50,000 on Premium, plus basic network discovery on Premium and 30-plus import adapters.
• ● An enormous marketplace and an excellent API, so almost any workflow you can describe can be built — by you, by a partner, or by an app someone already wrote.
• ● Atlassian is not going anywhere, and if your district already runs Jira for other departments the service desk shares the same platform, permissions, and automation engine.

What to check before you buy

• You can no longer buy self-hosted. Atlassian closed Data Center to new customers on 30 March 2026, stops selling expansions to existing customers in 2028, and takes Data Center read-only at end of life on 28 March 2029.

  Basis: Atlassian's own Data Center end-of-life page states each of those dates and defines new customers as organizations that never owned paid Data Center seats before 30 March 2026.

• Assets is a flexible CMDB, not an ITAM product. It ships empty — you author the object schemas, types, and attributes yourself before it holds a single Chromebook, and Atlassian's own copy jokes that it can model 'people records? Fish?'

  Basis: Atlassian's asset and configuration management feature page describes it in exactly those terms; discovery is IP-network scanning, listed as a Premium addition.

• No device custody as a product concept — no check-out to a named student, no due date, no overdue list, no parent-signed agreement, no loaner pool, no lost or stolen lifecycle, and no damage fees. You would model all of it yourself in objects and workflows.

  Basis: None of those terms appear on the Assets feature page; ownership is an attribute you define, not a transaction the product understands.

• No SIS or rostering integration exists. Marketplace searches for ClassLink and Skyward return zero results, and searches for OneRoster, PowerSchool, and Infinite Campus return only unrelated token matches.

  Basis: Queried directly against the Atlassian Marketplace REST API. Atlassian also publishes no education vertical page — /solutions/education and /industries/education both 404.

• No student, guardian, or family concepts. The only end-user primitive is 'customer,' an unlicensed requester. There is no enrollment, no grade, no guardian relationship, and nothing that notices a mid-year transfer.

  Basis: Atlassian's pricing and feature documentation define customers as unlicensed users who can raise requests; no education-specific data model exists.

• Change management — the single capability districts most often cite as the reason to choose JSM — sits on Premium, at roughly two and a half times the Standard rate.

  Basis: Atlassian's plan comparison lists change management, advanced incident and problem management, the virtual service agent, and asset discovery as Premium additions.

• SAML SSO is a separate purchase. Enforced SSO, SCIM provisioning, and password policies come from Atlassian Guard, priced per user across your whole Atlassian estate — not per agent.

  Basis: Atlassian's JSM pricing FAQ states SAML SSO is enabled 'with a subscription to Atlassian Guard.' Guard Standard is $4.20 per user per month, bundled into Enterprise, and free under the academic program — so for a qualifying district the cost is nil, but it is still a second product to apply for and administer.

• Two metered dimensions make the bill non-deterministic: Assets objects past the plan allowance and virtual-agent conversations past 1,000 a month. A district that models every Chromebook, charger, and hotspot as an object should count objects before signing.

  Basis: Atlassian's pricing page publishes $0.02 per object per month and $0.30 per conversation over allowance.

How Chalk compares with Jira Service Management →

Sortly

The friendliest inventory app in this comparison and the easiest to actually start using — built for supply closets and job sites, priced by how many items you have, which is exactly the wrong meter for a 1:1 fleet.

Where Sortly is strong

• ● Every price is on the page, including a genuinely free tier, with no demo gate anywhere in the funnel.
• ● The lowest adoption cost in this comparison by a distance: folders, tags, photos and custom fields, usable by a building secretary in an afternoon without an IT project behind it.
• ● Strong mobile — iOS and Android with offline access, barcode and QR scanning, and label generation from inside the same app, so counting is a phone job rather than a scanner-hardware purchase.
• ● Alerting that fits consumables well: low stock alerts for reordering and date-based alerts for maintenance and repair schedules, with in-app and email notification.
• ● More reporting than the price suggests — activity history, inventory summaries, user activity, low stock and item-flow reports, saved custom reports, and report subscriptions delivered on a schedule.
• ● Real integration surface for a product this simple: webhooks, an API, QuickBooks Online, and Slack and Microsoft Teams notifications, plus purchase orders, pick lists, and check-in and check-out.

What to check before you buy

• Pricing meters unique items, and a 1:1 district's item count is its student count. At 5,000 items the published tier is $299 per month, and anything past 10,000 items is Enterprise quote-only — a mid-sized district is off the published ladder on device count alone.

  Basis: Vendor pricing page item limits: 100 free, 500 Advanced, 2,000 Ultra, 5,000 Premium, 10,000+ Enterprise.

• User licenses are metered too, and tightly: 1 user free, 2 on Advanced, 5 on Ultra, 8 on Premium. A technician team plus building staff crosses into Enterprise quickly.

  Basis: Vendor pricing page user-license limits per tier.

• No help desk or ticketing of any kind. A district running Sortly still buys a service desk somewhere else, and the two never see each other.

  Basis: Absent from the vendor's published feature list, which covers inventory, alerts, reporting and integrations.

• No MDM or device integrations at all. The published integration list is QuickBooks Online, Slack, Microsoft Teams, webhooks and an API — so ChromeOS, Intune and Jamf data is typed or imported, and serials go stale between imports.

  Basis: Vendor features page lists no device-management or directory connectors.

• No SIS or rostering integration and no student, guardian or enrollment concepts — nothing notices a transfer, a withdrawal or grade rollover.

  Basis: Absent from the vendor's feature list and from its industry positioning, which addresses inventory rather than student records.

• Check-in and check-out is item custody, not a school-year loan: no due dates on a student device agreement, no e-signature, no damage fee, no family balance and no loaner pool workflow.

  Basis: Vendor documents check-in/check-out alongside pick lists and stock tracking, with no agreement or fee concepts published.

• It is an inventory product rather than an IT asset lifecycle product — warranty expiry, depreciation, ChromeOS auto-update expiration and refresh planning are not in the published feature set, though generic date-based alerts can approximate some of it.

  Basis: Vendor features page covers custom fields, alerts and reports; no warranty, depreciation or lifecycle module is published.

• Hosted SaaS only, with no self-hosted option, and no SSO or SAML in the published feature list — so it sits outside your single sign-on estate in both directions.

  Basis: No self-host or source distribution is offered on the vendor site, and SSO does not appear on the features or pricing pages.

How Chalk compares with Sortly →

The third option: Chalk

If you are weighing Jira Service Management against Sortly, Chalk belongs on the same shortlist. It is the open-source K-12 IT stack: device inventory that fills itself in from Google Admin, Intune, and Jamf against a roster synced from your SIS, a 1:1 circulation desk with agreements and fees, repairs with parts and costs, a help desk that already knows who is asking, and a built-in SAML/OIDC identity provider.

• ✓ Self-host it free forever under AGPL-3.0 — the entire feature set, one binary, your infrastructure — or use the hosted version, priced by fleet size with no per-seat or per-student fees and the price ladder published.
• ✓ Built only for K-12: students, buildings, custody, funding sources, and ChromeOS auto-update expiration are native concepts, not custom fields.
• ✓ Writes back to Google Admin as a reviewed diff — every OU move, disable, and deprovision previewed before it executes — and serves a OneRoster 1.1 API so other district systems can pull the roster from Chalk.
• ✓ Fees are assessed and tracked without touching payment cards, keeping the asset system out of your PCI scope.