Our challenge is that there are many departments wanting the same information, in their own way, then also wanting to edit that data.
We have an instance where we are using a custom field to try to get information from a requestor via a custom form attached to a request in a project. We also have a custom form in the project for scoping of the project that has the same fields. The hope was that if the information was provided in the request, the scoping form would be auto populated. Then, if there was not the information provided we could enter it in the project scope custom form/field. Then we could also run a report across multiple projects for easy viewing and editing in weekly planning meetings.
Has anyone had success creating anything like this?
Topics help categorize Community content and increase your ability to discover relevant content.
If you have an issue form with a custom field and then create a task or project from that, the field will copy over (upon project or task creation) providing there is a corresponding form on the target object (task or project).
Also, you can create a calc field on an object that populates with the value of another object. Populating a field on an existing project from a task or issue my prove difficult because a project can have many tasks and/or issues. It won't know which task or issue to pull from. Some experimentation may be in order.