Hi everybody,
trying to search for additional issuelink rows - using jira cloud for sheets (which is a perfect tool to report JIRA issues related to epics and subtasks at the same time) - raised the following message. Please some help on this subject. I add that I have access to all issuelinks, so it should not be an authorization issue.
Hi Angélica, thanks for your answer, I do not know what could be the problem, but if I select columns from a new report this does not happen.
But, in my already saved report in which I used subtasks an epic link subfields, this does happen, check attached new screenshot
best regards
Marcelo
How did you solve it?
I'm getting the same error but with the Links issues fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Marcelo,
Welcome to Atlassian Community!
Testing on my local site and Google Sheets, I was able to select the Issue links fields and import the issues to Sheets, so I'm not sure if I followed the correct steps.
Is this issue happening when you select the field, when you click on Save or when you click on Get issues now?
Are there any other projects that you can use to test?
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again Angélica
Testing again I finally found out what the problem was
If you select issuelinks subfields first and then add subtasks subfields - the multiple field row expansion not supported - message shows up
If you select subtasks subfields first and then add issuelinks subfields - the multiple field row expansion not supported - message shows up
If you select issuelinks subfields first OR select subtasks subfields - the multiple field row expansion not supported - message does not show up
different purpose subfields conflicts each other, so for the time being is understood, but let me know your comments
Thanks and regards
Marcelo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the details, Marcelo.
I was able to replicate the same issue here when selecting both subfields for subtasks and linked issues.
Further searching, I found an internal ticket where our developer mentioned that this is expected. The row expansion functionality can be used only on a single column/field type at a time.
Hope this clarifies.
If you have any other questions regarding this matter, please let us know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
[DELETED]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.
Register nowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.