My organization uses a project intake process through which new requests are submitted via form. The fields of the intake form are connected to custom fields which then populate in the Asana project. Once there the tasks are approved and converted into a standalone project. I have noticed that the custom fields from the form show up in the written project overview, but they do not carry over as project custom fields upon conversion. In order to apply those fields again at the project level this has to be done manually. Is there a way to automate this?
This would be a game changing feature for large scale organizations. Or if not this, a way to intake full blown projects directly from a form intake process.
I believe the main obstacle right now is that a project only has fields if added to a portfolio holding those fields. But converting a task to a project does not have the ability to add to a portfolio. Until they add this ability, they wonât be able to add those fieldsâŠ
Yeah it makes sense, but itâs definitely a hinderance. It really feels more like a half implemented feature to be able to apply custom field values to projects but only in a portfolio view. Thereâs a general lack of ability to apply attributes to the overview of projects that feels like a major oversight.
I guess I should be flipping this to a feature request at this point.
Fully agree. I have manually moved the closed task into the project in order to have some historic data of the fields and then reopened it for any edits.
Haha @Bastien_Siebman, Iâm not sure but you may be right - it may be something they added later, I donât recall. Weâll give you the benefit of the doubt!
Phil, does this mean that if you add the project to a portfolio, the custom fields will be linked to it and then you can report out on the fields of the portfolio by grouping the custom fields as well?
This has been released and should be live. Make sure that the field you would like to carry-over is added to the library on the project and portfolio level. Once the task is converted to the portfolio, any global fields (fields added to the library) should carry over from task to the newly created project
Hello,
thank you for this, Iâm looking to solve the same problem. However, thereâs something that still doesnât seem to work: if the type of the custom field is - for instance - âsingle-selectâ of ânumberâ, the information is carried over correctly when the task is converted to project. If, however, the type is âtextâ, the custom field is blank when the project is created.
Do you think thereâs a solution to that? Thank you very much!
Istvan
If youâve followed the directions (same custom field added to both places), and it works for other types but not Text type custom field only, then try these troubleshooting steps, then please create a support ticket: see How to contact our Support Team.
