Traceability Analysis takes too much time to complete, hangs my browser
Problem
You are trying the traceability analysis but it seems to never finish, or it takes too much time to complete. Sometimes the browser shows a not responding message.
Solution
The time of the analysis directly depends on the number of issues and issue links to analyze. You may requesting too many issues at once, which takes a lot of time to complete. If you wish to reduce the display time, please follow the steps below.
The goal of these steps is to reduce to number of issues you are working with and focus the analysis. Make sure that yo limit the number of issues to display:
- Replace All Types by All Inward or All Outward, depending on the direction of the analysis
- You are using a favourite filter or a JQL query that focus the analysis on only the issues you are interested in.
- You have configured the view to only focus on a reduced number of issue link types and directions
- The depth of the analysis is not too big (5 levels is usually enough)
- Remove the Description cloumn, which usually contains a lot of information which is unnecessary for an impact analysis.
Sometimes, when the issues have several levels of dependencies, it may be better to display a couple issues at once. For instance, you can use the following JQL queries:
- Displaying one issue :
issue = KEY-1 Displaying a couple of issues :
issue IN (KEY-28, KEY-29, KEY-30, KEY-31, KEY-32)