We are looking at WF Kanban (again)...The fact that statuses have to be locked to be able to use them in Kanban is not ideal because we would be subjecting all other groups to seeing our status values embedded with theirs. We may need to look outside of WF to get the flexibility/convenience that my...

I noticed that if I use the regular search to look for a portion of a word or numbers that I do not get any results back. For example, if I have a Task that contains a number "00123456" in the Task Name, but I use "123456" in the regular search, it doesn't find my Task. Second example, If I have a...

Currently, when we receive an email that someone is requesting access, the email displays an indicator so that you can easily see if the request is tied to a project, issue, task.However, when you are using Home to look at an Access Request, no indicator is displayed. You have to click the link to ...

@Narayan Raum, thanks for starting this thread and to everyone for providing feedback. I have always found Workfront's approach to engage with us on the community refreshing. :) I received a notice this morning that a lot of the list changes were being rolled back, which I think is a good thing. Ho...

David, I like your suggestion to make them configurable! I can't believe this on hasn't had more votes by now. :)

Ran across this and upvoted your link....I was actually looking to see if expenses could be added on Issues....surprised you can't, especially since Issues are so easy to enable for groups to create work. I also agree that the overhead to convert Issues to Tasks is NOT fun...and in the case of some ...

I wanted to remove the predecessors from a number of tasks that I had selected on a project, using the the unchain option. I noticed that after issuing the "unchain" option, some predecessors still remained in place for some of the selected tasks. I followed up with WF support ticket and they indic...

We were looking at using unique Status values for Issue for a new Group that wants to use Workfront. As part of their implementation into our instance, they wanted the Status values display for Issues to be renamed to names that are more meaningful to their group.Ex. "In Progress" was to be rename...

Agreed need more flexibility over this. Would like to control what displays regardless of what Status is Locked, Defaulted, Optional, etc.

This is definitely an oversight in the product no only with Kanban but also Approval Processes. Visited with different Workfront resources at Leap to discuss. Also have tickets opened with our ASE in support and looped in our CSM and Sales managers. I'd really like to see this changed to be more ...