User sessions with higher client-side latency present task forms in increased time windows allowing duplicate submits. The UI tries to solve this with a form mask that prevents multiple "Submit" clicks, but in some cases duplicate submissions are possible, depending on network traffic affecting the client session.
Steps to Reproduce
1 - Using Chrome, emulate client latency with the built-in network throttling feature.
2 - Login an early Jakarta instance as administrator.
3 - Click Incident > Create New .
4 - Fill out the mandatory fields.
5 - Open Chrome Developer Tools.
6 - In Network tab, set "Throttling" to the slowest option: "GPRS (500ms, 50kb/s, 20kb/s)".
7 - Click Submit. Notice a slightly opaque form submit mask will cover the form, wait for it to go away after a few seconds.
8 - Click Submit again. Repeat as many times as the submit mask goes away to allow it. Observe the duplicate key constraint on Primary Key with a user-facing message asserting "Invalid Insert".
9 - Click Submit again. Observe two incident records have been created with the same task number.
Related Problem: PRB1077509