Traceability Report throws error when user does not have browse permission for sub requirement project

Description

Whenever the user generating the Traceability Report does not have permission to see one or more sub-requirements, it fails with a NullPointer Exception.

This error is misleading and the report should behave differently (Jira hides the non-browsable issues from the 'Issues In Epic' List, the report could follow the same behaviour)

Pre-conditions

• Have two projects (project A and B)
• Create an epic in A and a story from B in it
• Have at least one user (user X) who does not have permission to browse issues in a given project (Project B)

How to reproduce

1. Login with user X
2. Generate the report in the project A
3. The report will throw an exception

Actual result/Attachments

user X who does not have permission to see project B will face the below error:

Users with permission to browse project B will be able to generate the report

Expected result

1. For user X, who does not have permission, the NPE error should not be thrown. The report should behave differently for the issues the user does not have permission to view. The report could hide the issues and show a message saying the user does not have permission to view all the issues in this report - actual behaviour for Test issues in the Test lane of the report (see below image)