Removing Behaviour mapping that mapped to all issue types or request types will remove other mappings under the same project or service desk

Removing Behaviour mapping that mapped to all issue types or request types will remove other mappings under the same project or service desk with specific issue types or request types.

Steps to Reproduce

1. Simply create two new Behaviours in the Behaviour List page.
2. Map the first Behaviour to a project but all issue types (important).
3. Map the second Behaviour to the same project but with a specific issue type. Let's say: project TEST (Task).
4. Remove the all issue types mapping from the first Behaviour. (Both delete from Behaviour page or Behaviour Edit page will trigger the bug)
5. Refresh your page on the Behaviour List page.
6. You will notice all the project(specific issue type) mappings are removed as well from all the other Behaviours including itself.

Expected Behaviour

Only the project(all issue types) mapping are removed.

Actual Behaviour

All project(specific issue type) mappings are removed from all Behaviours.

Workaround

No workaround.

Additional Info

• Tested on Jira 8.13.11 with ScriptRunner 6.40.1.