Information in Table and Request Form
I love how now Wrike allows information from request forms to populate automatically within a table. However when this happens, the information disappears completely from the request form itself. If there was a way to choose what information stayed on the request and what can just move to the table that would be great! I know that you can just change the question back to "Description" for a quick fix but I want the information to appear in both the table and the request form.
Hi Kevin, thanks for this feedback! I think I understand, I have a question though just so I'm sure. When using Custom Field questions in Request Forms, you would like the chosen answer to map to a Custom Field, as normal, and also show up as text in the description of the task? Let me know if I'm missing anything.
Hello Stephen, that is exactly it! Our team likes to print physical copies of the request forms that they submit but the mapped information does not appear when that happens. If there was a way to retain that information in the request description as well as populate in the custom field, that would be of great help.
Hi Stephen
At least that would be what I would expect. If you have many forms the person receiving the form does not necessarily know what information was filled out in the form and if the description is missing information that was filled out that does not make sense. There is no disadvantage in having the information in a custom field AND the description but only having it in a custom field is dangerous!
@Beat & @Kevin, Thanks for your posts here. The idea of having Custom Field options in Request forms is for mapping to that field in Wrike, though I can see the advantages of having this detail in text format in the description field. Thanks for sharing and expanding on the idea here for other members to vote and discuss further and I've passed this information onto our Product team.
Some examples of why this is a helpful tool for our team
1. information in request form that is attached to the title might also be needed in description/custom field - it needs to be in the title as a quick reference for task, but it is also something we need to organize a report from later.
2. Some of our custom fields have security in place, since changes to custom fields are not documented in Wrike, but it also means those details are not shared with the rest of the team who need to know the details.
This discussion is exactly what I was looking for. Custom fields allow us to quickly collect and aggregate data for reporting and sorting, but that information is very important to the flow and layout of the description area as well. It really needs to be in both places.
This would be very helpful for several of our Wrike use cases as well. Is there an update in development?