Can not export custom fields anymore using the latest ver. Also: TF51535: Cannot find field Custom.TimeSpentSecondsRendered. about jira-azuredevops-migrator

[Alexander-Hjelm]

Regarding the first issue, have you tried the solution under: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md#3-how-to-map-custom-field

Regarding the second issue, it seems that your field is not present in the ADO work item tracking Process Template. You need to actually create the field first.

[timakamystery]

Regarding the second issue, it seems that your field is not present in the ADO work item tracking Process Template. You need to actually create the field first.

same config works ok w/the old ver. as mentioned.

[Alexander-Hjelm]

Not sure what the problem could be otherwise. The log is saying that the following field is required in your ADO process, but it could not be found: Custom.TimeSpentSecondsRendered

[timakamystery]

hi @Alexander-Hjelm

1. Yes, referring custom fields as per the other faq method using latest 266 ver worked, thx.
2. For the time fields working config for me is:

      {
        "source": "aggregatetimeoriginalestimate",
        "target": "Microsoft.VSTS.Scheduling.OriginalEstimate",
        "mapper": "MapRemainingWork"
      },
      {
        "source": "timespent$Rendered",
        "target": "Microsoft.VSTS.Scheduling.CompletedWork"
      },
      {
        "source": "timeestimate$Rendered",
        "target": "Microsoft.VSTS.Scheduling.RemainingWork"
      },

Exmple json looks like:

        {
          "ReferenceName": "Microsoft.VSTS.Scheduling.OriginalEstimate",
          "Value": "3"
        },
        {
          "ReferenceName": "Microsoft.VSTS.Scheduling.RemainingWork",
          "Value": "2h 55m"
        },
        {
          "ReferenceName": "Microsoft.VSTS.Scheduling.CompletedWork",
          "Value": "5m"
        }

But then on import it complains like:

[E][14:03:41] TF401326: Invalid field status 'InvalidType' for field 'Microsoft.VSTS.Scheduling.RemainingWork'.
[E][14:03:41] Work Item 1059777 failed to save.

Because the target field type is double. I'm using a py script to process the json-s after export to convert the values. Any ideas pls how to make it work OOB ?

3. Another separate q. We have a link entry in the link-map list, e.g.:

      {
        "source": "BH",
        "target": "System.LinkTypes.Related"
      },

In Jira it's: "BH | drives | is driven by". But such a link type doesn't get into a json and no errors/warning in the export log. How to fix this pls ?

[Alexander-Hjelm]

3. Is because you are trying to import a string value into a double type field. I'd recommend using one of the unrendered time fields instead, as these will have an unparsable format.

4. I'm not completely sure, but I'd reckon you would probably need to look under the hood to find out what the name/key of the link type is (e.g. via the rest api) and maybe not the display name.

[timakamystery]

regarding #2
when try unrendered like, get nothing present in the json

      {
        "source": "timespent",
        "target": "Microsoft.VSTS.Scheduling.CompletedWork"
      },
      {
        "source": "timeestimate",
        "target": "Microsoft.VSTS.Scheduling.RemainingWork"
      },

[timakamystery]

ver. 284
config:

      {
        "source": "resolutiondate",
        "type": "datetime",
        "target": "Microsoft.VSTS.Common.ResolvedDate"
      },

[E][10:07:14] Error mapping field 'Microsoft.VSTS.Common.ResolvedDate' on item 'ESSUITE-9134'.
[System.InvalidCastException] System.InvalidCastException: Specified cast is not valid.
   at JiraExport.JiraMapper.<>c__DisplayClass14_0`1.<IfChanged>b__0(JiraRevision r)
   at JiraExport.JiraMapper.MapFields(JiraRevision r): 
   at JiraExport.JiraMapper.<>c__DisplayClass14_0`1.<IfChanged>b__0(JiraRevision r)
   at JiraExport.JiraMapper.MapFields(JiraRevision r)

didn't face such an issue before

[Alexander-Hjelm]

@timakamystery

I assumed you have checked #834?

What version of Jira cloud/server are you running?

[timakamystery]

hi Alex
Jira DC v9.11.2
what to check @ #834 ?

[Alexander-Hjelm]

Ok!

Is it possible for you to build the source code and run the tool in an IDE? If so, can you set a breakpoint at this line (https://github.com/solidify/jira-azuredevops-migrator/blob/771e3a9d4af57160377a3acb51d95aa217ea3629/src/WorkItemMigrator/JiraExport/JiraItem.cs#L504C31-L504C31)?

And report back to me with a screenshot showing the value of prop.Value?

You can use the free Visual Studio Community Edition if you don't already have Visual Studio installed.

[timakamystery]

I have VSC. Never worked w/.NET but me being a devops the task above looks like a nice exercise. Will let u know, thx

[Alexander-Hjelm]

@timakamystery Of course, let me know if you need any help building the project. Setting up VS should be pretty straightforward, although it can be pretty memory heavy.

[timakamystery]

Rechecked my export log files. Last time it repro-d on 20/12 on ver. 284. On yesterday's export using ver. 329 - it didn't. Fixed ? :)

[Alexander-Hjelm]

It could very well be. We have fixed some issues related to various specific custom field types since 3.0.284.

But am I correct in my understanding that from 3.0.329 and onwards, the problem no longer appears for you? Or?

[timakamystery]

I've just did 1 migration yesterday using the latest at that point 329 and yes, it didn't repro. Will let u know if it changes. Thx

[Alexander-Hjelm]

Ok! Good to know, but would be nice to get to the bottom of it.

Let's keep this issue open, and feel free to tag me if the bug ever arises again.

The bot should close the issue in 30 days if no more activity is logged.

If I don't hear anything else, I will assume that everything is fine :D

[github-actions]

This issue is stale because it has been open for 25 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 5 days since being marked as stale.

[timakamystery]

repro-d again on latest 356

[E][17:43:11] Error mapping field 'Microsoft.VSTS.Common.ResolvedDate' on item 'ESSUITE-8024'.
[System.InvalidCastException] System.InvalidCastException: Specified cast is not valid.
   at JiraExport.JiraMapper.<>c__DisplayClass15_0`1.<IfChanged>b__0(JiraRevision r)
   at JiraExport.JiraMapper.MapFields(JiraRevision r): 
   at JiraExport.JiraMapper.<>c__DisplayClass15_0`1.<IfChanged>b__0(JiraRevision r)
   at JiraExport.JiraMapper.MapFields(JiraRevision r)

will try in debug (not sure when yet)
cc @Alexander-Hjelm

[timakamystery]

separate issue faced: Latest version does not export sprint information, it doesn't get into the json files. Workaround used: use ver. 308 for the export. @Alexander-Hjelm if need more details / separate ticket, can do that.. thx

[timakamystery]

@Alexander-Hjelm and 1 more q. when a sprint is completed, all open issues get moved to the next sprint, which makes the field to hold multiple values, e.g. Sprint: IVR-2402, CC-Sprint-67. Hence json files don't have an Iteration Path. Expected: Iteration Path is filled with the latest value (usually the currently running sprint). Any suggestions pls ?

log in debug mode has smth like:
[W][15:30:18] Missing mapping value 'Zen100, Zen101, Zen102, Zen103, Zen104' for field 'Sprint' for item type 'Task'.
[D][15:30:18] Mapped value '' to field 'System.IterationPath'.