---
title: "#jira-service-management articles | Hashnode"
description: "Explore 10 articles tagged #jira-service-management on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/jira-service-management"
---

Tag

# #jira-service-management

10 posts · 0 followers

[Kayabyte](https://hashnode.com/@kayabyte) · [Nov 12](https://hashnode.com/posts/how-to-calculate-on-call-pay-from-jira-service-management-schedules/6af5859e28fe69fb4f7ee4f1)

### [How to calculate on-call pay from Jira Service Management schedules](https://kayabyte.hashnode.dev/how-to-calculate-on-call-pay-from-jira-service-management-schedules?utm_source=hashnode&utm_medium=feed)

JSM Operations has no on-call pay report. How to get standby hours and pay per person from the final timeline: pay rules, categories, DST.

4 min read · [kayabyte.hashnode.dev](https://kayabyte.hashnode.dev/how-to-calculate-on-call-pay-from-jira-service-management-schedules?utm_source=hashnode&utm_medium=feed)

[Kayabyte](https://hashnode.com/@kayabyte) · [Nov 1](https://hashnode.com/posts/cc-a-whole-team-on-every-jira-service-management-ticket/6ae7abc0e9fcc5fee292d834)

### [CC a whole team on every Jira Service Management ticket](https://kayabyte.hashnode.dev/cc-a-whole-team-on-every-jira-service-management-ticket?utm_source=hashnode&utm_medium=feed)

A common ask from support leads: "Whenever a customer opens a ticket, our account team should be copied." In email that is a CC. In Jira Service Management there is no CC field for a group, and the pi

4 min read · [kayabyte.hashnode.dev](https://kayabyte.hashnode.dev/cc-a-whole-team-on-every-jira-service-management-ticket?utm_source=hashnode&utm_medium=feed)

[Kayabyte](https://hashnode.com/@kayabyte) · [Nov 1](https://hashnode.com/posts/jira-service-management-keeping-request-participants-in-sync-with-a-group-joiners-and-leavers/6ae79cc5995f78eaaaef29af)

### [Jira Service Management: keeping request participants in sync with a group (joiners and leavers)](https://kayabyte.hashnode.dev/jira-service-management-keeping-request-participants-in-sync-with-a-group-joiners-and-leavers?utm_source=hashnode&utm_medium=feed)

Adding a team to a request once is the easy part. The part that bites is next quarter: somebody joins finance, somebody leaves, and the requests already open still show last quarter's team. This is ab

6 min read · [kayabyte.hashnode.dev](https://kayabyte.hashnode.dev/jira-service-management-keeping-request-participants-in-sync-with-a-group-joiners-and-leavers?utm_source=hashnode&utm_medium=feed)

[Loomwise](https://hashnode.com/@loomwise) · [Oct 31](https://hashnode.com/posts/jira-service-management-make-comments-default-to-internal-note-or-reply-to-customer/6ae5d7d5f69c85c97b4a2b44)

### [Jira Service Management: Make Comments Default to Internal Note (or Reply to Customer)](https://loomwise.hashnode.dev/jira-service-management-make-comments-default-to-internal-note-or-reply-to-customer?utm_source=hashnode&utm_medium=feed)

How to set Jira Service Management comments to default to "Add internal note" or "Reply to customer": the site-wide setting and its limits.

4 min read · [loomwise.hashnode.dev](https://loomwise.hashnode.dev/jira-service-management-make-comments-default-to-internal-note-or-reply-to-customer?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Oct 15](https://hashnode.com/posts/claude-code-hits-a-jira-workflow-validator/6ad05e520b8183735186df0a)

### [Claude Code Hits a Jira Workflow Validator](https://leanzero.hashnode.dev/claude-code-hits-a-jira-workflow-validator?utm_source=hashnode&utm_medium=feed)

Claude Code moves a Jira change request through its workflow via the REST API. Two CogniRunner validators read the backout plan and rehearsal: 400, then 204.

25 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/claude-code-hits-a-jira-workflow-validator?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Oct 9](https://hashnode.com/posts/atlassian-team-26-europe-recap-and-highlights/6ac91ea1afc6888b1f2d2063)

### [Atlassian Team '26 Europe recap and highlights](https://leanzero.hashnode.dev/atlassian-team-26-europe-recap-and-highlights?utm_source=hashnode&utm_medium=feed)

Our Atlassian Team '26 Europe recap from RAI Amsterdam: the highlights in one list, the Closing Keynote, and what we learned as Jira and Confluence admins.

10 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/atlassian-team-26-europe-recap-and-highlights?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Oct 7](https://hashnode.com/posts/sentiment-analysis-in-jira-service-management/6ac5d2242e07d878ff25b86c)

### [Team '26 Europe in Amsterdam: Jira Service Management sentiment analysis in triage queues](https://leanzero.hashnode.dev/sentiment-analysis-in-jira-service-management?utm_source=hashnode&utm_medium=feed)

Jira Service Management sentiment analysis: the plan it needs, how to turn it on and the Sentiment = Negative JQL we validated. Team '26 Europe.

15 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/sentiment-analysis-in-jira-service-management?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Oct 3](https://hashnode.com/posts/one-person-two-jsm-customer-accounts-what-actually-clears-the-duplicate-after-an-email-change/6ac0b656eaebaa0a86a50491)

### [One person, two JSM customer accounts: what actually clears the duplicate after an email change](https://leanzero.hashnode.dev/one-person-two-jsm-customer-accounts-what-actually-clears-the-duplicate-after-an-email-change?utm_source=hashnode&utm_medium=feed)

One person, two JSM customer accounts in the reporter picker. Why removing them from the project cannot fix it, and the reporter reassign that does.

17 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/one-person-two-jsm-customer-accounts-what-actually-clears-the-duplicate-after-an-email-change?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Oct 2](https://hashnode.com/posts/microsoft-graph-to-jira-assets-user-ingestion/6ac03288489c39032a8025b8)

### [Microsoft Graph to Jira Assets User Ingestion](https://leanzero.hashnode.dev/microsoft-graph-to-jira-assets-user-ingestion?utm_source=hashnode&utm_medium=feed)

Ingest users from Microsoft Graph (Entra ID) into Jira Service Management Assets, including the parts the public Assets API does not document.

19 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/microsoft-graph-to-jira-assets-user-ingestion?utm_source=hashnode&utm_medium=feed)

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero) · [Oct 2](https://hashnode.com/posts/uploading-attachments-to-jira-service-management-cloud-assets-without-public-api-documentation/6ac006bfa0f57f8d7a9b1868)

### [Uploading Attachments to Jira Service Management Cloud Assets Without Public API Documentation](https://leanzero.hashnode.dev/uploading-attachments-to-jira-service-management-cloud-assets-without-public-api-documentation?utm_source=hashnode&utm_medium=feed)

Attaching files to Jira Service Management Assets objects is undocumented. Three calls: get upload credentials, push to media, link the object.

8 min read · [leanzero.hashnode.dev](https://leanzero.hashnode.dev/uploading-attachments-to-jira-service-management-cloud-assets-without-public-api-documentation?utm_source=hashnode&utm_medium=feed)
