Issue Summary

Users experience a 429 error (Rate-Limiting) when editing issues in the Issue Modal View on TMP Software boards with a large number of issues. This seems to occur due to a spike in API calls made by the system, leading to rate limiting.

Steps to Reproduce

1. Access a TMP software board with a high number of issues, including Sub-tasks (e.g., 600+ issues).
2. Add a custom field to the tasks/events on the board (e.g., a single-select field).
3. Open an issue on the board using the Issue Modal View.
4. Edit the custom field multiple times (approximately 10-20 times).
5. Observe the occurrence of a 429 error.

Expected Results

Editing issues via the Issue Modal View should not result in a 429 error, regardless of the number of issues on the board.

Actual Results

Editing issues in the Issue Modal View on boards with a large number of issues leads to a 429 error, as the system makes excessive API calls.

Workaround

To avoid the 429 error, users can open and edit issues using the Full Issue View in a separate window or tab, rather than making edits directly in the Issue Dialog Modal through the Board view. This prevents the excessive API calls that trigger the rate limit.

Additionally, after encountering a 429 error, users can wait approximately 5 minutes for the rate limit to reset, after which Jira becomes usable again.