Carry Over Original Project Name on Routed Issue | Community
Skip to main content
C
ChristineZh3
Level 2
August 12, 2023
Question

Carry Over Original Project Name on Routed Issue

  • August 12, 2023
  • 3 replies
  • 1396 views

Hello!

 

We are looking to track project change requests as issues on existing projects and would like to have those issues routed to a main intake queue so that they can be tracked and resourced. When I try to use a calculated field to capture the project name, it just looks to the project that the issue is currently living in, not the project that it got routed from.

 

Thank you!

 

Christine

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

VicSellers
Community Advisor
VicSellersCommunity Advisor
Community Advisor
August 14, 2023

Hi @christinezh3 - Unfortunately, it isn't possible to use a calculated field for this due to Workfront's configuration. The only seamless way to do would be to involve Fusion.

 

What I've done as a work around to this though, although it does involve a step for the user, is to add a typeahead field on the issue that shows project names and have the user associate the issue and its related project. I just tell the users, for training purposes, that it is needed for back-end system reporting.

 

Hope that helps!

C
ChristineZh3Author
Level 2
August 14, 2023

Thank you for confirming and for the workaround!

Madalyn_Destafney
Community Advisor
Madalyn_DestafneyCommunity Advisor
Community Advisor
August 14, 2023

Have you considered having a routing rule on a queue topic of the template used to automatically route to the team or user that will run with the issue? You can also set the default project in the routing rule to go to your main intake project, and have a column of that main intake issue View show the where the issue came from.

If this helped you, please mark correct to help others : )
C
ChristineZh3Author
Level 2
August 14, 2023

Hi Madalyn, thanks for the idea. That's how I currently have it designed, but am not able to capture the originating project via a calculated field once the request routes to the main intake project. How do you recommend showing where the issue came from?

 

Madalyn_Destafney
Community Advisor
Madalyn_DestafneyCommunity Advisor
Community Advisor
August 15, 2023

I'm not sure you need a calculated field, have you tried using Issue > Source as a column in your issues view? I THINK that should show where the issue came from...

If this helped you, please mark correct to help others : )
N
nryan2
Level 3
August 16, 2023

Have you tried using the Issue Path field?

Terms & ConditionsAccessibility statement

Loading footer...