We are being asked the same request. Certain fields they want a
character limit less than what's allowed now. If we could adjust this,
that would be helpful.
When creating a project from a template, the box area is small and only
accounts for a certain number of characters. Would like to expand that
out and account for the length of the template or wrap the template name
so users can read and entire wording.
I would also like this. I'm deploying a country based group and trying
to reduce the "noise" for them in the system and they see all these
approval processes and have inadvertently added to a project kicking off
notifications to users not in their organization. If we could manage
approval processes like we do templates, portfolios, projects, etc then
this would be better for us.
This is an ask all the time for our users. At the Project, Task and
Issue level an export to PDF or excel is being asked. The only work
around I've seen is to print the business case for the project level but
that doesn't help the task and issue level.
This is what our teams are asking for as well. They would also like to
see a connection with Outlook if and Out of Office time is blocked in
Outlook, it updates in Workfront on the calendar so not to set in a few
places.
Hi Lucas, We started down that road but there could be a number of
action items and we were looking for some smart logic to create more
(like risks and expenses adds on a new one when you fill one in) instead
of action "Action 1, Action 2, Action 3.....Action 20). We don't know
the number of actions it could be and that becomes and admin nightmare
to maintain. Thanks for the idea though. Thanks
Ability to track action items like you can with Risks with customizable
fields. For example, action owner, status, deliverable, date raised,
date to be completed. This could be on the issue, task and project
level.
In the Queue Set Up: Routing Rules: Default Assignee area, allow to
assign to multiple users upon entry. Only way to assign to 2 or more
users for a queue topic routing is to create a new team. Sometimes it's
not a full team but rather a couple of individuals. An issue can be
assigned to multiple users why can't the request route that way as well?