-
-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description containing some tables fails to migrate (ADF) #961
Comments
This is json dump of the description field from Jira: |
@eplnde I assume we are talking about the standard tables in jira? See screenshot: It seems like this is some kind of macro inside jira, and the data is never exported as proper html. So maybe there is another endpoint involved to get the html formatted table? Marking as feature request. |
No, this is a cust&paste table from excel |
Ah ok! Either way this feature will need to be implemented. |
@Alexander-Hjelm I think it would be good to at least add some warning that data is dropped as a "quick fix" |
We did some repro and we found that regular tables in jira (see my screenshot) are migrating just fine. It must be that bringing in table data from external sources like excel causes a problem. Will look into this asap, but this is not our highest priority at the moment. @eplnde, maybe there is a way to convert your data, like first creating a regular table in Jira and then pasting the data? Even if that is not optimal if you have a lot of data, of course. I'm not sure myself here. |
Aha ok! This is an excel function, right? I am guessing that default HTML tables in Jira do not support this function? |
yes, as mentioned in #961 (comment) |
Describe the problem
If the Jira description field contains tables with "merged cells", the are lost/dropped
To Reproduce
otput:
{
"ReferenceName": "System.Description",
"Value": "
For test of some AzDo migration issues
\n\n"},
Tool version
Attachments
Please attach the following files:
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: