Sign in to Community
Sign in to view all badges
Expand my Community achievements bar.
Approvals are a great feature within Workfront. Unfortunately, in their current state, their usability is limited. We are requesting improved options and flexibility for approval processes, including:
1. Specify actions (eg status change) to be taken if APPROVED.
2. Increase available options for REJECTION and APPROVAL - eg, change status, add an update, prevent edits, etc.
3. Add comments to rejection issue created (currently, they only appear under project updates instead of in the issue created by the rejection).
4. Add the ability to hold the project/task/issue status at a certain level until the approval has completed.
5. Make approvals an automatic, and enforced, predecessor of project tasks being ready to start.
Agreed. We have a need to use approvals in a more complex way as well. A few things we're looking to do:
Our organization has a need to have a task approval option to approve with edits. Currently, we hit approve and type in "approved with edits" into the comments section. However, the flaw in this system is that the task doesn't pop back into the team's queue to make the edits. They must manually remember to make the edits before the next task can truly start.
An ideal approved with edits function would bring the task back to 0%, but it would not require another approval before the next task starts.
Bumping this thread. This would be a great feature to have as we are trying to put more governance on our requests, especially as it comes to branding and content. Approval processes would be a logical way to help! Please advise on where this is in he roadmap...hopefully, it still is 🙂
I also have a suggestion for Approval Processes. Right now, when an Approval Process is attached to a Project, Task, or Issue, any time that object is put into the status it triggers the Approval Path. What I would like to see is a configuration setting that would only allow each Approval Path to trigger once per Approval Process use.
For instance, I have a Project that triggers an Approval with three Paths‚ÄîCurrent, Go-Live, and Complete. Once the Project goes Current, and then moves on to another status, I don’t want that Project to be sent out for approval again for the Current Status, even if it is put back into it. Then the same would apply to the other Statuses on that Approval Process as well.
I think the current setup is fine, as there is definitely a use-case to re-trigger Approval Paths multiple times. Could we get a setting when configuring the Approval Process to toggle whether each Path could only trigger once, or multiple times?
@Hong Liu What could solve for that quite well would be one status that triggers approval, ie Seeking Approval which, when approved, would move the project into a status of Current. Then you can go from Current > Planning > Current as many times as you possibly need without re-triggering approval unintentionally. That's the solve I would love to see for this area of Workfront.
Katie George. thanks for your reply. this is really a good idea which worth of trial.... Let me meet with our business users and see. thanks.
Hi Hong‚Äîglad you saw my reply! Unfortunately, my idea is not quite possible yet, although I do still recommend using an alternative status than Current to trigger approvals! If you use "Approved" it will say Approved - Pending Approval, then *manually* the project owner can move Approved projects to Current. At least until the day the functionality requested here is available...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.