---
title: "Discussion on \"Jira Service Management: keeping request participants in sync with a group (joiners and leavers)\" | Hashnode"
description: "Discussion on \"Jira Service Management: keeping request participants in sync with a group (joiners and leavers)\". 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"
url: "https://hashnode.com/posts/jira-service-management-keeping-request-participants-in-sync-with-a-group-joiners-and-leavers/6ae79cc5995f78eaaaef29af"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [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

Nov 1 · 6 min read · kayabyte.hashnode.dev  
Read the article

-   [#jira](https://hashnode.com/tag/jira)
-   [#jira-service-management](https://hashnode.com/tag/jira-service-management)

## Written by

[Kayabyte](https://hashnode.com/@kayabyte)

@kayabyte

  
[View profile](https://hashnode.com/@kayabyte)

Small studio building apps for Wix, HubSpot and Mac. Practical write-ups on what works.

Small studio building apps for Wix, HubSpot and Mac. Practical write-ups on what works.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
