Custom Form Carry Over When Converting from Issue to Task/Project

[#1]

It would be nice if we didn't have to create 3 copies of each forms, so that when a form is filled out during a queue, the data in the form automatically carries over when the issue it creates is converted to a task or project. Currently, we have to create 3 versions (issue/task/project) of each form, and then the supervisor doing the conversion/assignment of an issue to a staff member, has to ensure they are adding the task or project version of the form when they convert that issue and assign the task, so that the data the person input during the queue process isn't lost.

[#2]

When you convert an Issue to a Task or a Project, if you have the exact same fields on the custom form for the associated Task or Project object, the fields from the Issue are automatically applied to the custom form for the object you are converting it to. We use this as part of our project creation process. The user has to fill out an Issue to request to have a new project setup. The fields on the custom form are also contained in a section on our Project Custom form. When we convert the Issue to a Project, the fields from the Issue are updated to the Project. Hope this helps.

[#3]

Kelly,

Thank you for your response, and I understand how it works now. But it’s not very intuitive. I shouldn’t have to create an issues form, a task form and a project form, and when converting from an issue to a task, then select the correct task version of the form to ensure the information is migrated during the conversion. That should be automatic, and I shouldn’t have to upkeep 3 versions of the form.

Regards,

____________________________________

Ian Plamondon

[#4]

Ian, with our workflow, our custom forms on projects often have more fields (additional fields for out PMs / Leads to fill out when they get the request that the requestor wouldn't know) than the initial issue form. I think that is the thought behind them doing this. However, it's not on everything for us, and it is a pain as you pointed out. I think there should be options to generate the additional forms (for projects/task) and even if you want to be chained replicas of each other. When we've had big changes or additions, I spend a lot of time updating the issue form and then re-doing all again for the project form. Would be great if I could also say: Update these two other forms with these changes as well. I'm with you. There has got to be better, more efficient way.

[#5]

I agree. Maintaining 3 forms is a lot of overhead & creates more room for error. I'd like an option to allow us to link the forms if we choose to.

[#6]

Also, I have people filling out the form inside a Task, accidentally, and then nobody can find it, and it can't be moved to the Project level so that it can become visible. Try explaining the difference between a form for Tasks a form for Projects, when they look exactly the same, and the resulting eye rolling might kill you.

[#7]

Even if we have to maintain three different forms - it would be fantastic if the custom data would automatically transfer during conversion instead of needing to sort through the list of available forms and select the correct one to transfer the data. We have had more than one instance of information being lost because the wrong form was selected from the drop down in the process of converting an issue to a task.

[#8]

This would be more helpful if there are changes to the custom form. Making the same changes to 3 levels of forms is very time consuming and leaves room for mistakes.

[#9]

It is difficult to maintain forms when you have to always do two to make sure they match. I can understand that some people might want more information on the Project form (we don't), but it would be nice if you can have the option for it to copy or not.

[#10]

Upvoted! If form isn't completely blank carry it over to the resolving object. Better yet, custom forms should be made agnostic to a record.. just like custom fields are agnostic to forms. Why have multiple copies of the same darn form for main objects when you can just have one.

[#11]

Hey everyone,

Thanks for upvoting this idea!

I'm marking this idea as "Planned" and it is included in our product roadmap.

At the meantime, please continue adding your use cases here so that we can have more background for solution design.

Thanks,