Pass Request Form fields to the Task
The Request Forms address needed data from the requester. But they mostly neglect the task owner and what he needs to know and how he can use that info. There are two key weaknesses.
1. There is no way to insert fixed text in the request form that is passed to the task owner. The only solution I've seen is an unsatisfactory hack (put the passthrough copy in a question, which unnecessarily exposes it to the requester.). As an admin I find it important to provide accompanying info to the task owner so he knows what to do with the entered data, the metadata so to speak.
2. There is no way to pass requester-submitted controls (listbox, checkbox, etc.) with the requester selection to the task owner so he could change it a later time. This really is the general form of 1. above that extends it to all current Question data types.
Now custom fields and templates (I've seen those requests on this Forum) could be used in part to accomplish this. But I envision an easier fix.
Instead of calling each form field a Question, I'll just call it a Form Field. Each Request Form Field could have a listbox control field that sets how it's used.
- Question. Display to requester and pass answer to new Task (how it now works)
- Editable Question. Display to requester and pass the control with requester response to the Task.
- Task Direction. Do NOT display to the requester. Just pass it through to the Task.
Thank you,
Marc
Would like to send a fillable form to an employee or team member for them to edit using the existing controls (dropdown, checkboxes, etc). Another workaround could be that tasks have this feature available, with some kind of permissions customisation. For example, user "X" can only edit "Y" Form Field or question.
I am finding out by experience that there is no way to pass parameters from a request to tasks within a project. An incoming request can populate custom fields, but these fields are not treated as global variables, they are not inherited down to the tasks and subtasks of the project. It appears that the current implementation assumes that each task may have its individual request form, which is only a trivial case of the interdependencies of tasks and projects. The same holds true for the Blueprints as well.
Is the product team addressing this issue?
Hello Vladimir Taft, welcome to the Community 👋🏻
Thank you for posting and sharing your feedback. There is a post here, could you please check it out and let me know if this is similar to your use case?
If so, please upvote that post too. Currently, that is not in the short-term roadmap of our team but I've passed on your feedback and I'll be sure to update this thread if anything changes. Here is a useful article explaining what happens after we receive Product feedback 🖊