Description - Need request queue/forms to be able to include proofs as a document.
Why is this feature important to you - requesters need to reference proofs of their needs as a part of their request when submitting to our team.
How would you like the feature to work - We need to form to funtion/include access to proofs as documents they can include.
Current Behaviour - no where to include proofs as a document on a request in the form.
Is it an existing proof? If so, you could just send a URL, right?
It is! but then in our scenario - the web developer that needs access to the proof for their referenced requested work would not have access to the proof/then the proof is left outside of the new project that will be converted to from the request. Need a proof to be included at the form level so it can be a part of the request to get converted into a project.
So… it's an existing proof, in a project. And you want to be able to upload it via a form to a request that will carry it over into another project made from that request.
Then this proof will be in two projects, right?
Does it have to be a proof? and not just a document?
It does need to be a proof because we are leveraging the interactive proofing tool and has to have annotated comments completed before the request is submitted - so it must be able to be submitted in a request queue form and then converted to a project from there.
the workflow is:
Requester reviews a website > makes a proof (wireframe) of comments/changes needed > requester submits that request to Web Development team > request is converted to a project for development.
So the new project that is created from the request needs the proof as its reference/direction and the proof is being created before tagging the web team is even needed.
So the real question here is can you move a proof from either a personal proof or a project proof (request queue) to another project (made from the request).
If they're making the proof before the project is made, where is that proof?
interesting - I did just test adding a document to the queue project and then adding a request to the the queue directly in the project and moving the proof to that issue, which kind of worked! Not the best experience for requesters who are used to just accessing multiple request queues through their requests app in the main menu, and that's how they interreact with other teams as well.
They'd essentially be making the proof in their documents when they need to because if they made it on the after the request was submitted the workflow would be out of sync and web team would have a request with out a ready proof to reference.
Here's my best guess at a workable workflow.
The requestor uploads a file and creates a proof in the specified request queue (not a personal proof).
The requestor then submits a request with a link to the proof.
The PM (or whomever) creates a project from that request.
The PM (or whomever) then goes to the original document and moves it to the new project (moves, not copies nor download and re-upload).
Talking it through has been super helpful, thank you very very much!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.