We are not trying to change our project methodology, so QA Analyst should be always aware of how the project is administrated in JIRA. Typically QA Analysts are not creating any extra documents, they are using X-Ray for test management, so the only documentation should be created in JIRA. Here is what is typically documented:
Test cases - with X-Ray test cases are reported as Test issue types, test cases are linked to correct user stories so it is clear why they were created and what they should test. More test cases can be created for one user story.
Test Plan - issue type for administration added to Jira by X-Ray. There should be one Test Plan for each project and all test cases on the project should be linked to that Test Plan. Test Plan allows to PM to see general overview of all test cases created for the project and also overview of testing results.
Test Execution - issue type for administration added to Jira by X-Ray. There should be one Test Execution for each Feature Sprint and all test cases on the project should be linked to the correct Test Execution. It allows to PM to see general overview of all test cases created for the Feature Sprint and also overview of testing results.
Reporting bugs - as we are in development phase during Feature Sprints, we usually describe founded issue to Comments section and we move the user story to Rejected state and assign it to CE for fix. Bugs are reported by our QA Analysts when it is not clear what was the root cause for the bug and from UAT phase to Go-Live. It is possible to use another way for reporting bugs, but it must be always approved by PM.
For details about testing methodology, see https://knowledge.pricefx.com/space/QAKB/4744871996/QA+testing+methodology