Project On Hold won't allow issues to travel to child project queue

[TaraMc2]

We have a parent to child project setup. Our parent project is configured to allow a smaller request queue for creative development. We have many people that contribute and enter requests within the parent project. When the Project Owner places the project on hold, the child request (issue) is not routed to the creative queue. Is there any way to allow the request to push through when the project is on hold? 

[skyehansen]

Can you give specific steps to what you're doing?

e.g.

- I have a "parent" project with a queue topic for Creative and a routing rule that moves the request to a project called "Creative Intake".

- If my parent project is set to status Active, and I click on New Issue and submit an issue, the issue gets moved to Creative Intake. - If my parent project is set to status On Hold, and I click on New Issue and submit an issue, the issue stays in my parent project. 

The reason I'm asking is that I'm not able to replicate your problem -- whether my parent project is set to Active or On Hold, the submitted issues are getting moved either way, which implies I've misread something in your original post.

[TaraMc2]

Thanks for the quick reply

We are entering a request off of an issue that has an auto-assignment to the Team Queue. The issue looks like it's assigned but it does not appear in the Teams Request Widget and no notifications are sent. If I change the project to "Current" the issue appears in the Team Assignments widget and a notification is received. 

Thank you 

[skyehansen]

gotcha. There's no travelling involved. It's about notifications and where it shows up. This is normal. Workfront widgets and notifications do not trigger when a project is on hold. You should either create a different status that is like an on hold status but equates to In Progress so work can continue to trigger -- or utilize a report that your team can access to do work.

[kautuk_sahni]

@TaraMc2 just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!