Multi-picker field issue - while moving a work item from one project to another project.

[Hemanthkumarmuthyala]

Hi Avi,

I hope this email finds you well. I am writing to request your assistance with an issue we are experiencing with cascading field created using your multi-picker add-on in ADO.

We have created a cascade field using your multi-picker add-on in project A. However, when we try to move a ticket from project B to project A, the cascade field is not reflecting in the ticket to update the value. But, we are able to see and update the field when we try to create a new ticket in the project A and moving the ticket within the same project from one WIT to another WIT.

We would greatly appreciate it if you could look into this issue and provide us with a solution as soon as possible. If there is any additional information or context you need to investigate the issue, please let us know.

Here are the steps to reproduce the issue:

1. Add a multi-picker field (cascade) along with the options and make the field mandatory in any WIT in Project A.
2. Try to move any WI that created in Project B (where there is no cascading field added in project B) to Project A.
3. Map to the WIT, where the multi-picker field was added in Project A.
4. Click on submit.
5. Not able to view the multi-picker field options, and as it is a mandatory field, we couldn't be able to save the ticket.

Thank you for your prompt attention to this matter.

Thanks,
Hemanth

[avih75]

When the multipicker fields arnt shown its mean that the csv file isnt fit (name,size,content) בתאריך יום ו׳, 16 בפבר׳ 2024, 10:14, מאת Hemanthkumarmuthyala ‏< ***@***.***>:

…

Hi Avi, I hope this email finds you well. I am writing to request your assistance with an issue we are experiencing with cascading field created using your multi-picker add-on in ADO. We have created a cascade field using your multi-picker add-on in project A. However, when we try to move a ticket from project B to project A, the cascade field is not reflecting in the ticket to update the value. But, we are able to see and update the field when we try to create a new ticket in the project A and moving the ticket within the same project from one WIT to another WIT. We would greatly appreciate it if you could look into this issue and provide us with a solution as soon as possible. If there is any additional information or context you need to investigate the issue, please let us know. Here are the steps to reproduce the issue: 1. Add a multi-picker field (cascade) along with the options and make the field mandatory in any WIT in Project A. 2. Try to move any WI that created in Project B (where there is no cascading field added in project B) to Project A. 3. Map to the WIT, where the multi-picker field was added in Project A. 4. Click on submit. 5. Not able to view the multi-picker field options, and as it is a mandatory field, we couldn't be able to save the ticket. Thank you for your prompt attention to this matter. Thanks, Hemanth — Reply to this email directly, view it on GitHub <#33>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIPBUI2UKXFZ2BLUOY5KSSTYT4IM3AVCNFSM6AAAAABDLTR3MGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZTQMBYHEZTGNI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Hemanthkumarmuthyala]

When we try to create the WI in the same project, we can be able see the field and can update. However, when the WI is moving from other project to the current project, the field is not reflecting to update.

[avih75]

Thats mean that the values arnt fit בתאריך יום ו׳, 16 בפבר׳ 2024, 14:10, מאת Hemanthkumarmuthyala ‏< ***@***.***>:

…

When we try to create the WI in the same project, we can be able see the field and can update. However, when the WI is moving from other project to the current project, the field is not reflecting to update. — Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIPBUIZUR4PMG5ZMSY3SOR3YT5EE7AVCNFSM6AAAAABDLTR3MGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBYGI3TMMZXGE> . You are receiving this because you commented.Message ID: ***@***.***>

[Hemanthkumarmuthyala]

Ok, thanks. Issue is solved by adding a global csv file.