Fusion: Convert issue to project currently does not bring over custom data

[#1]

Not sure if this will go anywhere because there probably aren't enough people following this channel to vote it up to get he required votes, but worth a shot.

Currently, when you use fusion to convert an issue to a project, the custom data doesn't come over. No biggie, you can then update the project with the info from the request.

However, if you have 10 form you need 10 flows. And if each form has 100 fields, you must manually map each field from the request to the project. Now take this further and you want to change the name or add a field.. Yep. Update the flow.

It would be AWESOME if we could either convert with a switch (include custom data) or have a sub-object that we could pull over for the custom data without mapping each item. If the key doesn't exist in the new project object, it is dropped. If it exists it gets mapped. Sounds similar to the "CONVERT ISSUE TO PROJECT" button in the user interface, no?

[#2]

Oh that's a big problem. We're looking into using fusion but if this is the case that completely turns us off of it. Especially if we ever have to change our intake forms, which is at about 400 fields (not all used at once) between the different forms that get added to our projects.

[#3]

Using a custom HTTP request, you can accomplish this...

The API call would look something like:

PUT

issue/ISSUE_ID/convertToProject?updates={"options":["preserveIssue","preservePrimaryContact"],"project":{"name":"Converted Project Name","templateID":"TEMPLATE_ID"}}

You would just need to put the data in the right spots for the card. I don't remember all of them off the top of my head

[#4]

Thanks Dale - that's why I thought that the convert issue to project card would map all the data over from the issue to the project. Instead it brings over a set of blank custom forms which then needs to be mapped.

[#5]

You can make this happen automatically if you copy your ISSUE custom form but make it a PROJECT form. All fields must be EXACTLY the same in both forms - the only difference is that one is project and one is issue.

Then add the PROJECT custom form to the project template you will be using to create your project spaces. You do this in the template > template details > custom forms (at the bottom) > add custom form > select the PROJECT custom form.

We use this all the time so your CSM should be able to show you.

NB: if any fields are changed in the ISSUE custom form in the future the updates will need to be reflected in the Project custom form as well.

[#6]

Yep. that's the way it has worked for years. and it does work in creating forms and when you use the Convert Issue to Project button. However, in FUSION, the convert issue to project card does not operate that way.

[#7]

I have a fusion convert to project module that does not seem to be bringing the populated custom data from the issue to the newly created project. Can anyone tell me how this module is supposed to operate and if the custom data is supposed to be transferred? If this is not the intended purpose of this module then what would be the best approach?

[#8]

I noticed a little addition in the Fusion Workfront Misc Actions->ConvertToProject options and that is the copyCategories option available when you check "Show advanced settings".  I played around with this and when you enter: true.  It will copy over the custom forms from the issue to the converted to project.  I am thinking I will update the Fusion template to illustrate this...at least with instructions on how to do it.  I'm going to go ahead and mark this as investigating...and ask for our product team to confirm.