-
Type:
Suggestion
-
Resolution: Low Engagement
-
None
-
Component/s: (Advanced Roadmaps) Search & Filters
-
0
Problem Definition
Enabling DEBUG on com.atlassian.rm.jpo.issueloading.lucene.issue.querying.explanation will have each "Issue sources" diplayed for a particular Plan.
It is impossible to correctly associate the "Issue Source" seen by Portfolio to the respective Issue Source JQL/filter/board/project used in the UI perspective - by just looking at the logs.
Example: UI view
(project = PLUTO AND issuetype in (Bug, Story, Sub-Task) AND Team = "Planet" OR project = PLUTO AND issuetype in (Epic)) AND (resolved is EMPTY OR resolved >= -90d) ORDER BY Rank ASC (project = VENUS AND issuetype in (Bug, Story, Sub-Task) AND Team = "Planet" OR project = VENUS AND issuetype in (Epic)) AND (resolved is EMPTY OR resolved >= -90d) ORDER BY Rank ASC
Example: logs
2019-03-11 20:13:25,054 http-nio-localhost-8080-exec-159 url:/jira/rest/jpo/1.0/backlog DEBUG user 1213x111111x1 xxxxx localhost /rest/jpo/1.0/backlog [c.a.r.j.i.l.i.querying.explanation.DefaultIssueLuceneExplainerFactory] Issue Source Query: +((+projid:20600 +(type:1 type:10001 type:5) +customfield_11500:57901) (+projid:20600 +type:10000)) +((-nonemptyfieldids:resolutiondate +visiblefieldids:resolutiondate) resolutiondate 2019-03-11 20:13:25,304 http-nio-localhost-8080-exec-159 url:/jira/rest/jpo/1.0/backlog DEBUG user 1213x111111x1 xxxxx localhost /rest/jpo/1.0/backlog [c.a.r.j.i.l.i.querying.explanation.DefaultIssueLuceneExplainerFactory] Issue Source Query: +((+projid:14906 +(type:1 type:10001 type:5) +customfield_11500:52515) (+projid:14906 +type:10000)) +((-nonemptyfieldids:resolutiondate +visiblefieldids:resolutiondate) resolutiondate
Suggested Solution
Have additional logging to associate the "Issue Source" to its respective JQL/filter ID/board ID/project ID.
Why this is important
The association would easily help in identifying the slow query used in a particular Plan from multiple Issue Sources used.