Issue Default Custom Forms | Community
Skip to main content
Heather_Kulbacki
Level 2
Jan 28, 2021 2:01 PM UTC
Solved

Issue Default Custom Forms

I'm thinking this may be an Innovation Lab thing - I don't see a way to currently do it, but thought I'd start here to see if someone sees something I don't.

Currently within a project's edit features, you can go to Task Settings and set up a custom form(s) to be added to all newly created tasks by default. You can also set it to add an Approval by default.

I'd like to be able to add custom forms by default to all new issues created within a project as well.

SamanthaIsin
SamanthaIsinAccepted solution
Level 7
Jan 28, 2021 5:23 PM UTC

Just for the heck of it I went in and messed around. I found that if I opened the queue details I could add a custom form to the queue without publishing the project as a request queue. When I went in to create a new issue from the project the custom form was there. Is this what you're trying to do?

9 replies

Level 4
Jan 13, 2025 5:36 PM UTC

Found this thread while searching Experience League for a solution to our needs. 
Having been a few years from the original post, it would be great to hear if there's been any developments on this front or if anyone has discovered creative workarounds. 

We are building out request queue forms for Change Orders issues in which we can define a specific custom form with mandatory fields. We would like to route these incoming issues to the relevant project/task to keep them closely associated. We will have to do this with another touch-point by an intake team.

It would be great if a user, who is already familiar with the relevant project/task, could navigate directly to the respective project and submit an issue directly but still be presented with the relevant custom form. This would eliminate the need for a separate intake team to review and move the issue.

Translate
Level 2
Feb 23, 2021 3:06 PM UTC

I join the proposal, I think it is very necessary to speed up the load of issuing a project with it or the custom forms assigned by default or default.

It also helps to omit the inclusion of features and information to issues in projects.

It would help greatly for all project issues considering that they can be a large number of both issues and projects.

Please consider it as an improvement

Translate
Anna_Asatryan
Employee
Feb 19, 2021 3:03 PM UTC

Thank you Samantha, thank you Elena!

That's correct, ideally we would like to separate the request queue setup from the issue setup but my investigation showed (thanks for the use cases Samantha and Elena presented) that we will need to keep the ability to have advanced configuration and routing for the issues on the regular projects as well. We are not yet there, but we will need to work towards that in the future.

Translate
Level 2
Feb 23, 2021 3:23 PM UTC

Hi Anna Asatryan (Workfront, Inc.)

I think it is very necessary to speed up the loading of issues with the same characteristics in the projects and to avoid not including the required custom form in any issue.

It would be great to default to isssues of a project custom forms as in projects and tasks.

In my organization a significant number of projects are managed per year, this initiative would be of great help both for us and for all WorkFront users.

Translate
SamanthaIsin
SamanthaIsinAccepted solution
Level 7
Jan 28, 2021 5:23 PM UTC

Just for the heck of it I went in and messed around. I found that if I opened the queue details I could add a custom form to the queue without publishing the project as a request queue. When I went in to create a new issue from the project the custom form was there. Is this what you're trying to do?

Translate
Heather_Kulbacki
Level 2
Jan 28, 2021 7:06 PM UTC

I'm going to give that a try. If it works, it serves my need. I just wish it was as easy and intuitive as the way all new tasks can have a form added to them.

Translate