Thanks for the explanation, Rahul.
I understand the limitation although I still think the duplication makes it very hard for the information to be consumed in Sheets. If you think about the reasoning behind people using Sheets with Jira, it's certainly related to the ability to consume that information by manipulating, extracting, and using it for statistics and reporting. In my use case, I automatically pull data from Jira on a schedule and consume that through very complex formulas in Sheets. And with the duplication of records, it becomes practically impossible to address those situations through formulas or without consolidating those rows into one row manually - which completely defeats the purpose of the automation we do in Sheets.
I also understand that fields that may have a lot of information such as the ones you've mentioned make it difficult for them to be in the same row but on the other hand, duplicating records simply because I need to know the sprint name or goal doesn't make any sense.
For larger field content such as worklog comments, I wouldn't mind seeing them consolidated in the same row with a breakline between them. Anyway, I'm surprised to see people actually ask for row expansion...
Again, it makes a lot more sense to have them in a single row. Row expansion should be an optional feature that you can select instead.
Also, the current UI doesn't inform users about the duplication which really leads them to believe this is a bug, not a feature.
Sorry but I strongly believe you guys went the other way from what's more intuitive without even communicating that in the UI upon fields selection.
Not sure if there's a solution to this but just wanted to throw my perspective out there.
Thanks again.
Cheers.

Hi ricardo67 ,

 I am one of the developers from Product Integrations team. This is really a suggestion as categorized by lalmeida@atlassian.com originally in this ticket.

Lot of our customers were requesting for row expansion functionality (especially for fields like worklog and comments), what that essentially means is for these fields since the data cardinality cannot be visualized in a single row we expand the rows and duplicate the data when/if such fields are selected.

We understand that this can be a bit confusing but this provides a better visualization for further utilizing native sheets functionality using table/columns/headers.

To show all the fields data in a single row is really not possible, for example consider this case, you have an issue with 15 worklog records attached to it and you import such an issue with the fields worklog.authorEmail and worklog.comment. How would the issue displayed in sheets in a single row for such data? Also note that other issues in the import might have different number of worklog records. If you dont want row expansion, you can remove the fields causing this, such as "Linked Issues", "worklog" and "comment" etc.

Kindly let us know if you have any further questions around this.

Regards,

Rahul

Thanks for creating this ticket, Leonardo.

I'm not sure I agree with the approach this is a feature request though... From a user perspective, the option to select attributes of an object (such as Sprint.name or id) is nowhere defined as "sub-rows". Therefore, it should never cause the duplication of rows on the sheet output. Instead, the attribute should be aggregated to the same row of the ticket that it relates to.
Thus, I don't think there's anything the justifies the duplication of records on the final output... See, you're listing tickets with their respective information so it's a basic principle that there should NOT be any duplication there. It just doesn't make sense from a user perspective - reminding that the goal of any software is to achieve the definition of done and reach requirements satisfaction from what the "user" of that software identifies as needs.
All that to say, I still think this should be a "bug", not a feature request.
Thanks,
Ricardo