Users have high-priority need to take a Request that has been converted to a Project (using a specific template) and create a second project (with a different template) out of the original Issue/Request.
Users would be able to browse from Request list and see all projects created from original request.
Currently users are limited to just tracing just one project (aka "Resolving Object" back to a Request. If you try to take an issue and create a 2nd request from it, you get a warning message that the original resolving object will be overwritten. This will then make information incomplete in the Request Routing Dashboards and Request Queues and perhaps other places.
We would want the flexibility to create multiple projects from one Request and keep a traceable history from the Request tab and routing Dashboards.
Agreed. We typically get one request (issue) for a full campaign with multiple components. We create a campaign (program) and multiple projects. The problem is that the original request/issue can only have 1 resolving project. I want the original request to be resolved by a campaign/program and/or multiple projects.
I'd love to see it go both ways. I often get several requests that get rolled into 1 project and would love to be able to show them all resolved by the same project.
I'd love to see it go both ways. I often get several requests that get rolled into 1 project and would love to be able to show them all resolved by the same project.
I'd love to see it go both ways. I often get several requests that get rolled into 1 project and would love to be able to show them all resolved by the same project.
Yes, we need a request/issue to covert into a bunch of projects and/or connect a request/issue to a program/campaign. We almost always have multiple projects that stem from one campaign request.
Ex: Holiday Campaign request goes to projects: customer email, dealer email, creative, web pages, dealer printed materials, etc.
Thank you for the submission! We think this is a good enhancement to the Workfront platform overall and this product area in particular!
Workfront currently prioritizes large-scale, foundational enhancements such as the new Reporting experience and changes to the core data model, so this item does not fit in our near-term roadmap. As such, I am marking this as Declined now, but we'll keep this in our backlog for the improvements for this area so that we can revisit the decision in the future.
We are exploring a pilot to use one request issue for multiple resolving projects. The idea is for the Stakeholder to submit a full campaign brief that multiple project managers will leverage for their projects
Could you leverage a custom form field to tag any resolving object with the request/issue ID#, so that reports could still be generated based off a similar (albeit manual) grouping? For instances with Fusion, maybe this could become an automated tagging/form fill process every time a request/issue is re-converted to a new object so that the relationship from the previous resolving object isn't lost.
