inline images in repro steps from Jira not coming after migration in azure devops

[shweta22992]

Describe the problem
Inline images in repro steps (in Item Info) from Jira not coming after migration in azure devops (checking in repro steps).
Instead of the image getting this - !image-2023-11-17-12-09-02-249.png|width=799,height=421!
Very similar to this github issue - #114
just that I am getting in repro steps the problem
Also tried to use the mapper - MapRendered in the mapping but after that the repro steps got blank in azure

To Reproduce
Steps to reproduce the behavior:

1. Try importing a bug with repro steps having images in it

Tool version

• Version of the jira-azuredevops-migrator tool - 3.0.115 (also tried on 3.0.250 but same behaviour)
  Attachments

Please attach the following files:

• config.json
• jira-export-log.txt
• wi-import-log.txt

config-agile.json
jira-export-log-231121-161953.txt
wi-import-log-231121-164942.txt

Screenshots

[Alexander-Hjelm]

Usually you will want to migrate the description to ReproSteps, like this:

      {
        "source": "description",
        "target": "Microsoft.VSTS.TCM.ReproSteps",
        "for": "Bug",
        "mapper": "MapRendered"
      },

Or is Repro Steps a custom field in your case? In that case, possibly related to #602

[shweta22992]

Yes Repro Steps is a custom field that we are using in which all the screenshots etc we put, in description generally just plain text we put in our case. Is there any way you can suggest to work out images in Repro Steps.
In issue - #602 it mentions first revision is migrated but in my case after using MapRendered I am getting completely blank in Repro Steps in ADO.

[Alexander-Hjelm]

Gotcha. Most likely it is because the tool is trying to append the string "$Rendered" to the field id, as this is how description and other HTML fields work in Jira. Custom fields do not work this way however, so a fix is required on our part.

I am marking this issue as a bug report.

[Alexander-Hjelm]

@shweta22992, can you run the exporter with the setting "log-level": "Debug" in your configuration, and let me know what the output becomes for your ReproSteps field in the log? It should say something about which field it is trying to export and what the transformed value becomes.

[shweta22992]

@Alexander-Hjelm attaching the export log file.
jira-export-log-231123-103627.txt
' to field 'Microsoft.VSTS.TCM.ReproSteps' is what I could see in the log.
Also if possible can you pls let me know in how much time can we expect a fix for the bug.

[Alexander-Hjelm]

I see a lot of these for example:

[D][10:36:50]    Mapped value '*Server: PSP*
*tFDB:  thinkfolio_222nathann*

*User: rfurbear*
*Portfolio(s)/Group(s):  Any* 
 * Make sure that this Admin option is set like this 

!image-2023-11-17-11-39-01-307.png|width=579,height=389!
 * Set up a CDS trades - click on Open OTC position and select CDS 

!image-2023-11-17-12-07-41-345.png|width=538,height=248!

 
 - make sure to set the deal date a day back . This a key point here . 

*!image-2023-11-17-12-09-02-249.png|width=799,height=421!*

 

*!image-2023-11-17-12-09-29-084.png|width=753,height=392!*
 * Save the trade at Working  and as you can see here the accrued  is positive and this is what the trademarketside will look like at this point. 

*!image-2023-11-17-12-11-15-937.png|width=628,height=259!*
 * Run a tE15 – with a specific load source with no data.- run te15 with sloadsource 'nope' 

!image-2023-11-17-11-16-25-901.png|width=549,height=283!

 

*Expected Result: Accrued doesn't change and there is no error* 
*Actual Result:* Accrued has become negative change and there is an error in the logs 

{*}!image-2023-11-17-12-19-44-651.png|width=649,height=245!{*}{*}{*}{*}{*}

 

*!image-2023-11-17-12-27-39-073.png|width=1234,height=724!*

{*}Screenshot(s){*}:' to field 'Microsoft.VSTS.TCM.ReproSteps'.

Which should indicate that the value got mapped correctly.

Unfortunately it is hard to give an estimate at the moment, since I'm the only resource from our side who is actively working on this project, and at the moment there are other pressing needs. We always welcome community contributions though. And if you need prority support, contact us at [email protected] to inquire about consulting services.

[shweta22992]

One point I missed to mention the above log comes when not using MapRendered and when I add this mapper then ReproSteps get miss from the log file. Attaching the log file after MapRendered.
jira-export-log-231124-124033.txt
Will discuss with my team regarding the priority

[Alexander-Hjelm]

@shweta22992 what field type is your Repro Steps field in Jira? I tried to reproduce the issue for Jira Cloud, but when creating a new field I cannot seem to find any field type that resembles anything like "Html text field" or similar. The closest field type I can find is Text Field (multi-line), but that one does not have support for inline images, etc. Only unformatted text content...

[shweta22992]

@Alexander-Hjelm it is just like the description field that we have for a bug in JIRA, it has type Wiki Style Renderer.

[Alexander-Hjelm]

Ok! It looks like only Custom fields of type "Free Text Field (unlimited text)" or "Text Field" supports the Wiki Style Renderer.
I will try and reproduce this problem as soon as I can,

[Alexander-Hjelm]

Issue closed with merge of PR #918, please reopen the issue and tag me if the problem persists.

[shweta22992]

@Alexander-Hjelm I tried the latest release but the issue is still there for me. Image doesnt come and if I use MapRendered then it becomes blank.
jira-export-log-231129-110224.txt
wi-import-log-231129-110256.txt

[shweta22992]

Also not getting the option to reopen, if you can pls reopen at your end . @Alexander-Hjelm

[Alexander-Hjelm]

Demoting to support issue.

As I stated in #919, please make sure you have read through the FAQ on mapping and troubleshooting custom fields, I suspect you will find your answer there: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md

I suspect that you have tried to enter the jira field name without using "source-type: "name"` in the configuration :)

[shweta22992]

Thanks, working now after adding the "source-type: "name" in config. Closing the issue.

[Alexander-Hjelm]

Perfect! :)