Hi All, We have serval projects that span multiple departments. One project may touch 3 different request queues. Today, we keep the requests separate because some of the work and communication needs to be separate. That said, there are points where these projects intersect and other departments need to be aware of information within the project. We are looking for a way to handle one of the approaches below:
The requestor to be able to reference previously created requests (issues) in a custom form that is going to another department (example: 1st request for the fall fashion issue goes to creative team, in the 2nd request we want to pull in the ID or name of the 1st request and have it populate a clickable URL in a report)
After requests are submitted, we link the related requests together for a specific project (example: Request is submitted to creative, editorial and operations for the fall fashion issue. Then tag/link the creative, edit and operations requests together so they can be pulled into a report and viewed in a single row.)
We've dabbled with using cross-project predecessors in a project, but have not been able to get the communication to work as expected. Specifically - when a CPP is created in project A, it doesn't show up in project B or notify the owner of the project. Any solution to link 'issues' would be very helpful. We're offering a free Wired T-shirt! Thank you! Ladell Fuqua Condé Nast | PubWorx Services, LLC
