Is there a workaround for the output mapping result limit? I'm working on a flow where a user can query the bot to return all of their tickets in JIRA, but I'm losing some data in the process when the mapping gets bigger. Using conversational plugin, not compound action.
Example Output Mappings:
Mapping 1
MAP():
converter:
key: item.key
project_name: item.fields.project.name
status: item.fields.status.statusCategory.name
summary: item.fields.summary
url: $CONCAT(["https://company.atlassian.net/browse/", item.key])
items: response.issuesreturns:
1. Project A – 38 tickets
2. Project B – 1 ticket
3. Project C – 1 ticket
4. Project D – 13 tickets
5. Project E – 32 tickets
Mapping 2
MAP():
converter:
assignee: item.fields.assignee.displayName
created: item.fields.created
key: item.key
last_updated: item.fields.updated
project_name: item.fields.project.name
reporter: item.fields.reporter.displayName
status: item.fields.status.statusCategory.name
summary: item.fields.summary
url: $CONCAT(["https://company.atlassian.net/browse/", item.key])
items: response.issuesreturns:
1. Project A – 34 tickets
2. Project B – 1 ticket
3. Project C – 1 ticket
4. Project D – 15 tickets
5. Project E – 5 tickets
Have following content activity:
If there are more than 20 results, return number of tickets by project name and ask user if want to see tickets for each project separately.
You are allowed to comment and check comments only for Project E project tickets at the moment. For other project tickets, advice user to do this directly via Jira.
Conversational plugin description:
This plugin is used to list all open tickets for user. When you return tickets back to the user, use the Summary, Key and URL fields from the API response for each record.
The plugin logs indicate that the payload and the final mapped output contain the expected data. However, the end-user interaction shows that the bot is presenting incorrect information.
