Issue Summary

Jira Server for Slack (Official) app not updating the status IDs to be notified during transition if the number of statuses associated with the project is more than 100. It has been observed that this can also occur when a project has less than 100 statuses associated.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create multiple workflows in the project. 
2. Make sure that the count of all the statuses used in all the workflows of the project is greater than 100.  Say create 105 statuses and associate all of them to any of the project workflows.
3. In the Slack notifications screen add notifications for issue transition. And select a recently created status. (That is created after the first 100 statues )
4. 
5.  
6. Select statues that are the most recently created ones. 
7. Hit Done. 

Expected Results

The status that's selected gets added. And upon checking the list again we see the status that is selected before is reflected in the dropdown as checked.

Actual Results

We see the transition is showing the status to All instead of the selected status 'Archived'.

Only the first 100 statues in the order of creation will get added. For the rest of the status values, though they are selected on the screen, they do not get added to the table with a SQL error. 

2023-07-03 11:44:42,703+0000 http-nio-8080-exec-3 WARN admin 704x89x1 knqjvc 49.204.24.107,172.50.0.1 /slack/mapping/SOFT [c.a.j.p.s.dao.impl.DefaultConfigurationDao] Unique constraints are violated, falling back to update.
 

Workaround

If possible remove the obsolete status values and bring down the status fields count to under 100 that are associated with a specific project. 

OR 

Update table  "AO_B7D8D8_PROJECT_CONFIG"  to update the "VALUE_UNLIMITED" column to include the comma seperated status ID's.