Old subject: Allow Duplicate Emails across workfront environments (Doesn't this hinder workfronts growth potential?)Scenario: Your workfront instance is using the default workfront authentication, so you setup a username and password inside of workfront not through an SSO IDP. Company A : Adds bob@...

We'd like to be able to put longer than 9000 character messages into updates. We really only need to do this sometimes when we're copying external emails into workfront.

Agree with everything everyone's been saying in here,Maybe this would be set at a Project Settings area or maybe even the Team settings area.Team settings already have an option for what clicking done sets the status to, so adding an option for what the status should be when someone clicks Work On i...

Great idea!Here's another example of basically the same problemRight now workfront request queues have a "global" (to all queue topics within the root queue) setting for show the following selected fields to all users Description URL Assigned To Status Priority Severity Document Upload Primary Conta...

Currently when commit dates change on a task it sends an approval to the Project Owner. This approval doesn't follow the approval workflow used everywhere else in workfront it's a click button in the task instead of in the My Work -> Approvals sectionI don't understand why the approvals are not list...

Problem: You cannot sort by project completion date for issues (It works for tasks)

Problem: Updates that our clients make sometimes go into places where no one will be notified (We try to train them, but it'd be nice if we didn't have to) Possible Solution: It'd be great for our use case if we could set either a User setting or Project setting that would be something like "Do not ...

Our current workaround to this is to have a report that looks at all issues/tasks to make sure at least some time was logged to them.

Problem: Not everyone is logging time for each update they post. Possible Solution: It'd be great to force that each update from our team/group had to have some kind of time associated with the update.

Slacks thread implementation is a pretty great place to gain "inspiration" from. https://get.slack.help/hc/en-us/articles/115000769927-Message-threads . Another solution that would work for me is if workfront made an option to remove threads in general.