Ability to change the routing/"Path" of a submitted request

[#1]

Would love to have the ability to change the routing/"Path" (located in Issue Details tab / Overview Sub-tab) of a submitted request? It happens when the Requestor incorrectly selects it from the get-go so it does not appear in the correct team(s) queue.

Since the Queue Topic can be edited, it would be nice if it would automatically change the Path associated or simply have the ability to change it manually.

Thanks in advance!

[#2]

Thanks for submitting this idea. It would be great for all users.

[#3]

We're having the same issue as Giselle. I understand the path is a record of how the request was submitted, but some of us use this information in order to group categories and when the path is wrong we can't get this grouping right by just changing the topic name.

[#4]

This would make reporting and team holistic views comprehensive. I find this to be a serious flaw in the system, and would love it to be reviewed/enhanced.

[#5]

Should be able to Edit the Topic Group and Queue Topic of an existing Request. In our organization, we had to re organize our Request forms due to organizational hierarchy changes. Couldn't find any way to update the existing Requests path to match the new org hierarchy structure. This feature would help us to resolve the issue.

[#6]

This feature is quite important especially since Workfront has a similar feature for moving tasks to the right project.

If someone submits an issue/request in the wrong request queue, the same should be movable to another request queue within the same project or to a specific request queue in another project.

[#7]

This is key! If we can move requests between queues/projects, we should be able to move them between or change the queue topic. We can't ensure that our reporting by queue topic is accurate given some user error.

[#8]

Hi everyone,

Thank you all for the feedback!! While the potential value of delivering this enhancement is clearly evident, we don't have this effort planned and prioritized for our roadmap in the coming 12 months. As such, I'm marking this idea as Not Planned but please continue upvoting it and providing your use cases in the comment section below, that will help us during the ongoing evaluation process of the Idea Exchange.

‚

Best regards,‚

Vazgen‚ Babayan

Senior Product Manager, Workfront‚

[#9]

What does it mean when an idea posted to idea exchange goes from the status "Not Planned" to "Archived"?

[#10]

This topic came up in the Grow Track Experience Makers event today during the Q&A session of the "Calculated Fields Everyone Should Know (and How to Report in Them!)" segment with Anthony Imgrund. The request was to change the path of a submitted issue within a request queue.

As you can see it is "Not Planned" with only 590 points, however it got some buzz during that Q&A so maybe we need to make a little noise to bring it back up as an idea...?...

[#11]

Bumping this thread for reconsideration. It's frustrating when requesters make a mistake and have to resubmit just because we couldn't change the path destination.