Issue Summary

When a Slack channel is created from a JSM incident that has a team as a responder, only the user who was on-call the first time is consistently added to the Slack channel. Future incidents continue to add this original on-call user, instead of the user who is currently on-call for that team.

This suggests that the on-call responder is being cached and reused, rather than resolved dynamically from the current on-call schedule at channel-creation time.

Steps to Reproduce

1. Create a team (with at least two users) and enable Operations / On-call for the team.
2. Ensure User A is currently on-call in the team’s schedule.
3. In a JSM project:
   1. Create an incident.
   2. Add the team as a responder.
   3. Use the incident’s Slack / Add channel (or “Create Slack channel”) action.
4. Observe that User A (the current on-call user) is added to the Slack channel.
5. Update the team’s on-call schedule so that User B is now the current on-call user.
6. Create a new incident in the same project.
7. Add the same team as a responder.
8. Again use Create Slack channel from the incident.

Expected Results

When a Slack channel is created from an incident where a team is a responder, the user who is currently on-call for that team is added to the Slack channel. When on-call rotations change, subsequent incidents must add whoever is on-call at that point in time, not a previously on-call user.

Actual Results

It seems the on-call user seems to be cached and is added every time a slack channel is created from an incident when a team is allocated as a responder.

Workaround

Manually add the user into the slack channel.