Using ROVO to analyse issues is only returning answers in small batches

[George Abdo]

Hi All,

I tried a query in ROVO to analyse last months issues in JSM (around 1400) and provide a summary table with keywords/categories and the number of issues for each category. It took me a bit of screaming and cajoling but eventually ROVO gave me the table with the categories and the number of issues and it looked great.

I tried to do the exact same thing (i copied and pasted the original query but changed the filter for a list of around 600 issues) but no matter how hard I try or scream or rephrase, I cannot seem to get ROVO to give me a table for all the results. It is stuck at analysing on 40 issues or sometime 38, but never listing the full results in one table like the first time I tried.  

My query looks like this:

Analyse ALL the issues in [JQL filter on my service project] to extract keywords from the Summary and Description fields then categorise them based on these keywords.
Use the following strategy to analyse them:

For each issue, retrieve the summary and description.

Analyse the text for keywords and group issues into categories (up to 5 words per category).

Count the number of issues in each category.

Present the results in a two-column table: Category | Number of Issues.

Ensure the total number of issues in the table matches the number of issues returned by the filter.
DO NOT generate a table that only shows a subset of the issue. The table MUST categorise all issues

Any suggestions for making this work. I'd like to re-use this process in future for reporting purposes.

[Christopher Yen]

Hi @George Abdo 

I gave this a try and I can get it to analyze more records but never the full amount, I'm guessing it really prefers to sample data rather than run each record line by line. I always get a result about 40 - 60 shy of the full count but if you're okay with just a larger sample analysis adding steps and validation rules like below helps. It seems to like analyzing 20 records at a time from my experience.

Analyze ALL the issues returned by this JQL filter:

created >= -7d
AND project = SD
AND type IN ("Service Request", Incident)
ORDER BY created DESC

Step 1: Confirm the exact total number of issues returned by the JQL filter. 
Step 2: You MUST analyze that exact number of issues (no more, no fewer). 
Step 3: If you cannot process them all at once, process them in batches (for example, 200 issues at a time) and then combine the batch results into one consolidated table. 
Step 4: For each issue, use the Summary and Description fields to extract keywords and group issues into concise categories (up to 5 words each). 
Step 5: Count how many issues belong to each category. 
Step 6: Present the results in a two column table:

Category | Number of Issues

Validation Rules:
- The TOTAL number of issues in the table MUST exactly equal the number of issues in the JQL filter. 
- If the totals do not match, automatically re-analyze the missing portion and merge the results before outputting the final table. 
- Do not stop after a partial sample; continue until all issues are categorized. 
- At the bottom of the table, include a “TOTAL” row that equals the filter total.