🪲 Reference field values do not carry over when task is converted to project

I am considering this a bug until told this is expected behaviour.

When a task is converted to a project, any values of a reference field do not carry over onto the resulting within a portfolio with the same reference field. I’m assuming this is an omission in the code.

I have tested this three times in two different environments with different reference fields - same result.

@Forum-team , could you please escalate as this is part of a business-critical workflow we are currently building for one of our customers? Thanks!

2 Likes

Nasty bug there :slight_smile:

1 Like

Good catch, thanks for flagging @Richard_Sather! I’ve escalated it internally and will circle back in your thread once we have more information.

1 Like

Hi @everyone,

Good news! The issue where reference field values do not carry over when a task is converted to a project has finally been resolved! :tada:

Please give it a try on your end and let me know if you run into any remaining bugs or issues with it. Thanks for your patience while this was being worked on! :raising_hands:

1 Like