Change Rotation Participants starting from their NEXT rotation
Asked by Michael Edwards:

Given a rotation: (ignore the override)  
![before.png](https://community.atlassian.com/t5/image/serverpage/image-id/177075i30F4B7CE885FDFC2/image-size/large?v=v2&px=999 "before.png")

Can I remove the blue participant s without modifying any of the rotation prior to their next rotation?  

In particular this is annoying because right now the current rotation is ended and the next rotation starts EVEN THOUGH THESE ROTATIONS ARE NOT IMPACTED BY THE REMOVAL OF THE BLUE PARTICIPANT. Even with the override, you can see the shifts moving around even though they should not be impacted by the removal of the participant.  
![after.png](https://community.atlassian.com/t5/image/serverpage/image-id/177076iF2A095687BD6D859/image-size/large?v=v2&px=999 "after.png")


Answers:
author: Nick H
body: Hi [@Michael Edwards](/t5/user/viewprofilepage/user-id/4701548) ,

When a user is removed from a rotation, that rotation will be rebuilt with the remaining users from the **Start Date** set on the rotation.

So, in some cases, this can cause an issue where the dates/times for users left in the schedule are shifted. To avoid this when editing a rotation, it's best to reset the Start Date to a day/time that reflects which user should be on-call, and then to double check that the Final Schedule matches what you're intending:

![sched11.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/177077iAFC70A338C9CE95E/image-size/large?v=v2&px=999 "sched11.jpg")

Hope that helps. Let me know if you have any other questions.

comments: author: Michael Edwards
body: I reset the "Start on" date to the start of the current rotation and it looks good. Importantly (and probably the reason most people don't touch the start date), historical rotation information was preserved.  

This worked because J was first in the participants list already, but if it was someone further into the rotation list I would have to figure out the right start date in the past to ensure the current participant remained on call. As a feature request: it should be possible for Opsgenie to automatically determine this for me (or hide the complexity entirely).


author: Nick H
body: Glad that worked! I *believe*newer schedules have this functionality, but I don't think it applied to older schedules that were created before this was rolled out. For example:

![sched12.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/177091i4CD1E0E9B8646F7C/image-size/large?v=v2&px=999 "sched12.jpg")![sched13.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/177092iE4552780328A18A5/image-size/large?v=v2&px=999 "sched13.jpg")

\^ You'll notice the order of the participants in my second screenshot was automatically rearranged to reflect who is on-call after User 2 was removed.


author: Michael Edwards
body: :-O  

I want this. Where can I track changes like this where I need to recreate existing configurations to get cool new features?


author: Nick H
body: Engineering will typically create an in-app announcement for new features that can be viewed here in your Opsgenie:

![ann1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/177268i94391D5F5AB759C3/image-size/large?v=v2&px=999 "ann1.jpg")

A badge icon will appear for new announcements. You can also subscribe to these under your Notifications tab to receive emails as well:

![ann2.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/177269i1971BBCABE784FA3/image-size/large?v=v2&px=999 "ann2.jpg")


Tags: cloud