Referencing 'Request' fields in a calculated field

[GeraintJo]

Hi,

This seems really simple but I can't find the answer.

I've created forms to use to allow people to raise a request (issue) - from within a project.

Once that request has been triaged - a task is added to the project to deliver the items required.

A dedicated form is attached to the new task to display the details pulled down from the project request.

I've done this successfully referencing fields entered when a request is entered through a project Q - eg  

{project}.{DE:CS - MAKE - COPY - Channels}

What do i use instead of {project} to successfully reference the item from the request created from within the project

The form is attached to the request - not the project - so adding {project} at the front doesn't work

Nor does using issue, iss, request... etc

And I can't find any info telling me what this field should be when referencing a task/request in a calculated field

Thanks

[KellieGardner]

You should be able to add "convertedOpTask" to the front to reference the resolvable issue/request fields.

[GeraintJo]

Thanks Kellie,

so I've got this calculated field in the form attached to the task

{convertedOpTask}.{DE:CS - RETOUCH - Type}

CS - RETOUCH - Type  is the field in the form used in the project 'Q details' - that is filled in when a request is made against the project.

But it's still not showing correctly against the Task.

[skyehansen]

are you converting the request to a task? I'm having problems picturing how the information is going to get onto the task without this link.

[GeraintJo]

Hi

Hi,

The 'request' form is attached to the project under a Q topic and is used to create the Request.

It is not used to create a task within the project.

We do that manually using an existing template.

In a task within that template - the task form is attached and should reference some items from the above request form.

Hope that helps

Geraint

[skyehansen · Accepted solution]

I don't believe there's a way for an unconnected task to reference a request's form fields without some help, which you can provide either by linking the two (having the request resolved by the task's completion for example, or via a Fusion automation. 

[GeraintJo]

Thanks,

I was beginning to think that.

And If I use 'create task' from a request/issue - I have to add forms to the project settings as to use when adding tasks - I've got to add multiple forms with the user then having to remove the ones that don't apply !

Great scenario for FUSION to automate - when we have the skills to use it !!

Thanks for your help