Jira Service Management

Pricing is for Service Collection, which includes more than Jira Service Management. Do not assume every bundle app, AI allowance or Premium incident/change feature belongs to the Free Jira edition.

Check the specific change approval, incident escalation, customer portal and data-hosting requirements against the intended edition before migration. No authenticated configuration or performance was tested.

For teams using Jira Service Management Cloud, review the service space's Customer sharing setting before handling sensitive requests. Atlassian says request participants can view, comment on and receive notices about a request; customer sharing controls who can be added and can be disabled. Work item security can still prevent a participant from viewing it. Test a non-sensitive request with the intended customer roles and confirm its participant list and notifications before putting confidential details in the portal.

For a company-managed Jira Service Management Cloud service space, inspect the resolution SLA's start, optional pause and finish conditions and the goal's working-hours calendar before treating a target as elapsed wall time. Atlassian says a timer can pause while waiting for a customer, and only the calendar's working hours count. Ask an admin to try a non-sensitive request spanning a customer-wait state and closed hours, then check the actual timer and edition settings in the intended tenant.

Jira Service Management Cloud can bring a Confluence-linked knowledge base into the help center for customer self-service. For linked Confluence Cloud spaces, admins can set article visibility to licensed Confluence users, logged-in help-center users, or Anyone. The Anyone option exposes articles to web search and appears only with a paid Confluence Standard-or-higher plan, subject to portal restrictions. Before adding internal guidance, ask an admin to check the linked space and test a harmless article under both a customer login and a signed-out browser; confirm the Confluence plan and permissions in the proposed setup.

For a team-managed Jira Service Management Cloud space on Standard, Premium or Enterprise, a project admin can choose how customers open attachments from notification emails. Atlassian documents a portal-login route or a secured link that needs no login; anyone with that link can download the attachment. Links expire after 28 days, and changing the attachment setting invalidates previously generated links. Before sending sensitive files, ask an admin to confirm the chosen mode and test a harmless attachment with the intended customer, including whether the recipient can open it as expected.

For a company-managed Jira Service Management Cloud space that accepts requests by email, check the request type assigned to each connected address before adding form fields. Atlassian says Summary and Description must be visible and other visible fields optional; another required field prevents customer emails from creating work items. Ask a space admin to check that mapping and the incoming email logs, then send a harmless test email and confirm it reaches the intended queue before relying on the channel.

If customers must choose approvers in a company-managed Jira Service Management Cloud space, ask a space admin to check both customer-sharing permissions and the request form. Atlassian says the sharing setting must allow customers to search within their space or organizations, and the form must include Approvers or a multi-user picker field. Customers can add individual approvers, not groups. Before rollout, try a non-sensitive request with the intended customer roles and confirm the right people are selectable and the approval reaches its intended step.

Before placing sensitive context in a Jira Service Management Cloud request, compare Add internal note with Reply to customer using a harmless sample and the intended roles. Atlassian says internal notes are team-only, while customer replies appear in the portal and normally notify the customer. If an internal comment is later converted to public, customers can see it in the portal; when Public comment edited notifications are off, they receive no email about that conversion. Ask a space admin to check the setting and verify comment visibility directly rather than treating email delivery as the record of what customers can see.

For Jira Service Management Cloud teams that need post-incident reviews, check the Service Collection tier first: Atlassian places this advanced incident feature in Premium or Enterprise. A post-incident review created from an incident automatically links it as the Primary incident and can later be exported as XML, Word, PDF or to Confluence; Confluence export needs an active license and connected product. Before relying on this as the after-incident record, have an admin walk through a harmless sample, confirm who can read the work item and exported copy, and verify the intended export destination and retention process.

In a company-managed Jira Service Management Cloud space, check portal Channel access separately from request-participant sharing. Atlassian says an Open portal can admit anyone on the web when the site allows anonymous help-center access; a visitor then supplies an email to raise a request and sets a password to log in and view it. Restricted access requires customer self-registration to be disabled and admits customers explicitly added by agents or admins. Before handling sensitive requests, have an admin compare site and space settings and rehearse with a harmless external address to confirm who can submit and later view a request.

Jira Service Management Cloud Forms can show or hide a section based on an earlier radio, checkbox or dropdown answer, so a portal request can ask only relevant follow-up questions. If an answer must feed Jira automation, reporting or JQL, an authorized admin can link that form field to a Jira field, but the field types must match. The same Jira field cannot also appear on the request form or be linked twice in one form; linking a field already on the request type removes it from that request form. Required fields, including a linked Summary, cannot sit in a conditional section. Before rollout, ask an admin to preview both branches with harmless sample answers and check the intended work item and report fields in the team's tenant.

In Jira Service Management Cloud, confirm how new requests are shared with the reporter's customer organization. Atlassian says its site-wide No option makes the share field default to No one, but customers can still choose to share. For a stricter project rule, Atlassian documents an automation that clears Organizations when a request is created. Ask an authorized admin to use a harmless test request and compare what the reporter and a second organization member can see before sensitive requests enter that workflow.

For a Jira Service Management Cloud virtual service agent pilot, do not treat an abandoned conversation marked Resolved as a customer-confirmed fix. Atlassian says Auto-close nudges after five minutes of silence; if the customer selects No or remains silent another 24 hours, a prior matched intent or AI answer makes the record Resolved, while neither makes it Closed. Matched and AI-resolved conversations can count toward Premium or Enterprise assisted-conversation usage; test-mode and Slack test-channel conversations are excluded. Compare fictional matched and unmatched abandonments with a separately escalated work item, then check the current plan allowance and usage report before forecasting costs or resolution rates.