Create Work Items shows correct details in chat but the wrong space in refine/edit

[Kyle Reddington Kent]

Hey folks :)

I've noticed unusual behaviour with the Create Work Items tool that I haven't seen reported, I wonder if some users have seen similar behaviour.

When using the Create Work Items tool in Rovo, even with an agent that is just a simple chat with no other setup, there is sometimes inconsistencies shown between the details in the chat's Create Work Items final 'create' confirmation screen, and the full edit screen shown by choosing 'refine.'

Specifically, the space shown doesn't always match up. When working with the agent to select a space, the chat shows the correct space, the created ticket has the correct space, but the refine/edit screen shows the last browsed space.

I've observed similar with the priority field.

This happens most often if a bit more back-and-forth happened since the space was first mentioned. However, even immediately after having the chat confirm in an ordinary response what space will be targeted, and that final Create Work Items confirmation showing the correct space, the refine/edit space will still be wrong.

This strikes me as a limitation with this tool rather than something we could prompt it out of.

Any ideas?

[Arkadiusz Wroblewski · Accepted solution]

Hello @Kyle Reddington Kent 

Try out this controlled reproduction:

1. Check out Space B.

2. Start a new chat in Rovo.

3. Ask it to create a task in Space A with a specific priority.

4. Make sure to verify the confirmation card.

5. Open Refine and look at the Space and Priority.

6. Go ahead and create the task, then compare it with the new Jira work item.

7. Do the same thing again, but switch A and B this time.

In case Refine keeps showing the last space you browsed, while both the Rovo confirmation and the Jira item show the right space, that would be pretty solid evidence for Atlassian.

Also, give it a shot once with the standard Rovo Chat and once with a custom Agent. If they both act the same way, it might rule out the Agent instructions as the issue.

From moment the UI is showing a different value than what’s actually being created, I think it’s definitely something Atlassian should look into as this was actually recent rolled out.

If you can reproduce it, please open an Support Ticket with Atlassian.

Best,

Arek🤠

[Kyle Reddington Kent]

Hey @Arkadiusz Wroblewski , thanks for this! I've done a few such tests already and grabbed some screenshots internally, so I'll go ahead with a support ticket. Thanks for the sanity check!