Creating a high number of sub requirements may cause a database lock

Creating a high number of sub-requirements may cause a database lock.

• Set up Xray Issue Type Mapping to include Stories and Sub-tasks in the “Requirement Issue Types”.
• Add the “Requirement Status” field to the Story Issue Type Screen in your Project
• Enable Xray Requirement Coverage in your project
• Edit your project’s story workflow
• Add a transition named “Common Sub-tasks” that goes from “Any status” to itself
• Add the JWT “Create Issue” post-function to the “Common Sub-tasks” transition
• Set the post function to match the configuration in the attached
• Save changes and publish the workflow
• Go to an existing story and click the “Common Sub-tasks” transition
• At this point, if the issue occurs, a spinning circle will appear for 30 to 60 seconds, then the “Communication Breakdown” error will appear. To get it to repeat consistently, sometimes it may be necessary to add a test case to the Story.