How can I configure my agent to display JQL query results in a table format, sorted in proper chrono

[Gabriel Viger]

Hello Rovo community!

I am struggling to instruct my Rovo AI agent to display a JQL query results in a table format, sorted in proper chronological order.

Here are the instructions so far:

You are an assistant focused on monitoring requests assigned to the request type "Request for New Software Procurement" in the Techno Service Desk service management project.

Communicate in a clear, concise, and professional manner, focusing on actionable next steps.

Maintain a neutral and supportive tone, encouraging timely resolution of requests.

Export this JQL in a table: project = TSD AND "request type" = "Request for New Software Procurement (TSD)" AND statuscategory != Done AND status CHANGED BEFORE -7d ORDER BY created ASC

The table should display row number, URL, Created ASC, Last Significant Comment/Action (with date and author name and translated in english if in french), Next action needed.

Below the table, add common reasons why all these requests stalls listing all requests from the table above, should be clickable and sorted by common reasons and using a numbered list for each tickets.

Always answer based on the knowledge and documentation provided to you. If you do not have enough information, say so rather than guessing.

I've tried many variations of instructions to have it ordered by Created or Updated ASC  and there are always mistakes when the table is rendered.

Does anyone have a trick to have this done without any mistakes?

Cheers :) 

Gabriel

[Dr Valeri Colon _Connect Centric_]

@Gabriel Viger This is less about JQL syntax and more about how Rovo handles reasoning and formatting together. While Rovo reliably retrieves JQL results, it becomes inconsistent when it has to sort, interpret, translate, and render a table in one pass. The most reliable approach is to make the JQL the single source of truth for ordering (as you’ve done with ORDER BY created ASC) and then give the agent one deterministic table template to fill.

Tell it explicitly not to re-sort or reinterpret the results and to replace values only. Features like “last significant comment,” translation, or summarizing common reasons introduce extra reasoning that often causes ordering drift. If chronological accuracy matters, split the task into two scenarios: one that strictly generates the table, and a second that performs analysis below it.

[Gabriel Viger]

Hello Dr Colon,

Thank you for your reply.

I will try your suggestions and let you know the results.

Cheers! :) 

[Rebekka Heilmann (viadee)]

To be honest: I don't understand the purpose of this prompt from the prompt itself.

What are you trying to achieve overall?

What information should be pulled from the JQL result into what column, what information needs to be synthezised by Rovo?

I also don't quite understand the common reasons part. Should Rovo list reasons why these sort of tickets need longer? If so, shouldn't Rovo pull more data to provide that info?

Maybe Rovo has the same (or similar questions) and is therefore not giving you the expected results ;)