Currently, round-robin issue assignments in Jira Automation sort the users in the list by their Atlassian Account ID (AAID). It would be great if it could follow the user-specified order instead.

For example:
The round-robin assignment needs to follow a specific order like below:

1. User 1 (AAID: 637419xxxxxxxxxxx5)
2. User 2 (AAID: 6023aaxxxxxxx0x6df)
3. User 3 (AAID: 71xxx0:dbxxxxx-xxxx-xxxx-xxxx-xxxxxxx006)

But the current assignment behaviour will always follow the order below instead:

1. User 2 (AAID: 6023aaxxxxxxx0x6df)
2. User 1 (AAID: 637419xxxxxxxxxxx5)
3. User 3 (AAID: 71xxx0:dbxxxxx-xxxx-xxxx-xxxx-xxxxxxx006)

—

The Round-robin issue assignment in Jira Automation seems to reset the user assignment order for every rule config change.

For example, the user assignment order is set to:

1. User 1
2. User 2
3. User 3

But when rule configuration changes occur, the assignment order is reset to the first user. For example:

1. First rule execution: Issue is assigned to User 1.
2. Second rule execution: Issue is assigned to User 2.
3. Rule content modified
4. Third rule execution (first execution since the rule was last changed): Issue assigned to User 1 (User 3 was never assigned).

It'd be great if the assignment order is never reset.