Multiple requests routing to a single (ongoing) project | Community
Skip to main content
November 26, 2019
Question

Multiple requests routing to a single (ongoing) project

  • November 26, 2019
  • 1 reply
  • 389 views
Hi everyone, can anyone advise me or share the experience if managed in doing this: I would like to have a single request form (very simple - few fields only) that each time a user enters feeds into an ongoing project with a predetermined set of tasks. ( ideally also, picking up some information directly from the form) - In a nutshell, the requestor should have it easy to put in the information. - This information should route in some kind of automation/ transfer into an existing project. - Yearly work grouped in one project. This is not our standard way of working, we usually have a single request--> resolved by a single project, but for a series of small requests always with the same information I would like to cut some admin work and have it all in a single project. I have tried playing with request forms directly routing to a project, and also with task forms attached to the ongoing project... no luck, I am probably missing something and am a bit stuck with how else should I try. Any ideas? Thank you, Dea Dea Mijakovac
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Level 10
November 27, 2019
Hi Dea, We would do something like this with the API. Outside of that if you're trying to use a template for the tasks you need to convert the request to a project like you're previous method I think. But I think your previous way of doing it is better than you think. What is the extra admin work it's causing you? Usually any view/report you want to see can be accomplished with the multiple projects (using a program or portfolio to filter).