I’m using a form to capture initial intake requests from stakeholders, the answers are connected to custom fields in the board.
Right now, once the task has been created, all the custom fields are greyed out and can’t be edited. Is there an option to edit custom fields that are populated via form?
For example, if the stakeholder chose priority P0, but it’s actually P1, I would like to change that one custom field without creating another.
Looked but couldn’t find any way to do it, best very-far-from-ideal solution I found is to capture all responses in description instead and populate the custom fields manually.
Hi @Oron_Israeli , welcome to the forum 
This sounds strange. Could you possibly provide a screenshot?
You may also want to make sure you have edit permission (NOT comment only) for the project that the form is creating tasks in. Check who is the project owner and ask them (or other members with edit rights) to change your permission level to edit (this can be accessed from the ‘Share’ button, top right).
But the answer to your question is YES, you can change the form’s responses/values at any time once the form’s answers have been populated into a task.
And any edits you make to the custom field’s options/values will also reflect in the options within the form, if the custom field is connected to the form’s question.
Thanks! Of course, provided a screenshot below. Not sure if it’s related, but the intake first goes to board A where I have an automation rule to immediately move it to board B (board A is shared with multiple teams for intakes, so when a user selects my team’s name in the form, it’ll automatically be added to a different board).
o
Oh Richard, sorry seems like you misunderstood the question.
It’s not the values the user sees, that’s fine - I know I can edit those. It’s editing the user response after the form has been submitted.
I.e. - if in the screenshot above the user selected “Trust” but it’s actually a different team (e.g “CS”), I’m not able to change it.
Hey @Oron_Israeli , thanks for the screenshot. I thought the greyed out was within the List/Board view but now that I see it is within the Task Details panel, I can tell that the issue is basically that Board B does not have the custom fields of Board A, which should also be added to your field library.
You could simply solve this be changing your rule in Board A to ‘Add’ instead of ‘Move’ your tasks to Board B (see below snip). This is the reason why your fields become greyed out - they originally adopted the value from Board A but then when the task is moved to Board B, there is no such field in that project. If instead they are added, then the task will be multi-homed in both Board A & B, thus allowing the fields to be editable.
If, for whatever reason, you need to keep the ‘Move’ instead of the ‘Add’ then you have to:
- Go to Board A and select Edit for all the fields that you want to appear in Board B (so that they will become editable)
- Then in each Custom field’s Edit menu, select ‘Add to [your organisation’s name] field library’
- Then go to Board B and add all these custom fields, as you once did in Board A but instead you can simply add them by searching your field library (no need to rebuild them!) as per below:
If you do all the above, you should no longer have your fields greyed out 
1 Like
Thanks, copying the task instead of just adding and moving it solves it.
However, now I’m running into a different problem 
- I did have the exact same custom fields in the other board as well. But when the ticket is moved, now I have field from board A with response, and a field from board B that’s empty.
For example:
If I have “Priority” as P0 in the form.
I’ll have field 1 “Priority : P0”
I’ll also have field 2: "Priority: "
It doesn’t seem to de-dupe automatically if the custom fields have the exact same name. So is the solve for this adding custom fields to library and adding them to board B from the library rather than manually?
Thanks again! Did it in parallel and it does seem to work. Appreciate the help
1 Like
