Idea Exchange Promotion

[CalvinFold]

A version of this thread existed pre-ONE and I only just realized it isn't broadcasting on the daily feeds. I was encourage by Support to start it up again.

So, without further ado…if you want to popularize and get the word out on posted Idea Exchange ideas, post them here. Dearest reader, hopefully you Like this thread to keep tabs on new (or resurrected old) Ideas!

[jerflo]

Yep. Done. Thanks for bringing the duplicates to my attention @Kevin Quosig‚ @Heather Kulbacki‚

[ljanz]

Seeking more votes for making the typeahead field be linked to the object:

https://one.workfront.com/s/idea/0870z000000XhwIAAS/detail

[Heather_Kulbacki]

Please upvote: for Issue creator to maintain access to that issue even when that issue is moved to another project where they may have less access at the project level

https://one.workfront.com/s/idea/0874X000000sYizQAE/detail

[Heather_Kulbacki]

Please upvote: Allow more than Assignee to change Condition

https://one.workfront.com/s/idea/0874X000000sYj4QAE/detail

[CalvinFold]

This one seems simple but…I know too well how hard "seems simple" can be…

Document Count When Left Navigation Collapsed (NWE)

https://one.workfront.com/s/idea/0874X000000sYpbQAE/detail

[CalvinFold]

Sometimes minimizing something like the header without allowing customization makes things worse, not better…

Task Description and Reference Number in Header (customize header?)

https://one.workfront.com/s/idea/0874X000000sYqeQAE/detail

[JoeCa2]

Can you please upvote this idea?

Idea: Prevent users from logging hours on a task once it is set to "Complete".

https://one.workfront.com/s/idea/0874X000000sYqyQAE/detail

Please. have look and vote!

[jerflo]

@Joe Calandrino‚ and everyone else. I have consolidated the above idea into this one since they are virtually the same. Find the idea here: https://one.workfront.com/s/idea/0870z000000PSImAAO/detail.

[Heather_Kulbacki]

Please upvote this. It's rather lengthy, but we've run into some people seeing Commit Date as the Due Date on the Team Requests page and others seeing Planned Completion Date. It's confusing and I'm afraid the workaround may not be available once Classic is put to rest - it was available in Classic so it really should be available in NWE.

NWE Option for Planned Completion or Commit Date on Team Requests View

[Doug_Den_Hoed__AtAppStore]

Thanks Heather,

That one takes me way back (shout out to @David Cornwell‚ ; hope you're well, my friend!), but also makes me wonder...

If I gave you a magic wand (I know a guy) that you could use and have all commit dates reset to match their planned dates, would you wave it?

Regards,

Doug

[DavidCornwellLP]

Hey @Doug Den Hoed‚ - thank you for looping me in, buddy! This is a topic close to my heart that I'm still passionate about! This is extremely important. Not all customers want users to see Commit dates as Due Dates, as this can cause a lot of confusion when a Planned Completion Date is changed but users still see the old Commit Date. It is important to allow the PM to control the Due Date that is visible to users and have this not change when a commit date is set by a user.

I've voted for this and encouraged my colleagues to do the same.

Regards, David

[Heather_Kulbacki]

Haha, if anyone knows a guy, it's you!

I don't think I'd want to wave that sort of magic wand over everything. I'd need to get additional info from those who use it, but I suspect it's matter of "someone's told me they can't get me what I need before x date and I don't have access to change the planned completion, so I set a commit date and hope the project manager adjusts the planned completion date to match my commit date."

We also have other groups in our instance (and more wanting to join us) whose work is largely unrelated to ours, and they may have very different thoughts on commit dates than our team has.

[Heather_Kulbacki]

Thanks for the vote David! I was seeing commit dates that were later than the planned date and didn't even think about the possibility of that planned date being pushed out past the commit date at some point.

Either way it's unnecessary confusion for workers.

[DavidCornwellLP]

I can understand Commit Dates being of benefit if users and PMs are acutely aware of them and actively managing them. However, my experience is that more often than not, Commit Dates get set automatically to the Planned Date when the user clicks 'Work On It'. Then, when the PM later changes the Planned Dates of the Task, the end user doesn't go back and change their Commit Date (and the PM can't change the Commit Date for them). The user also still sees the Commit Date displayed prominently as the Due Date, which is where the confusion comes in.

In my opinion it would be better to default to users seeing the Planned Date as the Due Date, and then if they set a Commit Date that conflicts with this, use that to highlight the problem.

[Heather_Kulbacki]

I have a project manager who would be "the happiest lil clam" if this idea reached enough votes to make to the road map!

Typeahead field to be linked to the object

[ljanz]

New idea to upvote: Saving report defaults into lists for other reports

Right now, if I want to use that same sort of setting I created for a specific report but for a different (already created) report, I have to build it again from scratch. Sometimes they are quite complex so it takes some time to re-do.

I'd like to be able to save the filters, views and groupings I have set up in a report to appear in the lists for other reports. It would be great if after I created a new report, that I could save the defaults as a new filters/views/groupings in those drop downs. It could be an option at the end of the dropdown next to "Remove" and "New." Something like "Save default"?

[SarahNa]

Yes - this is great!! Upvoting now!

[CalvinFold]

This came-up during our NWE training, and support confirmed we can't do this as of now:

Customize "Copy to…" Defaults

https://one.workfront.com/s/idea/0874X000000oNrrQAE/detail

[CalvinFold]

We were a bit surprised this couldn't be done, and it creates a bookkeeping hassle:

Move a Project-Level Expense to a Task

https://one.workfront.com/s/idea/0874X000000oNrwQAE/detail

[SamanthaIsin]

Hey all,

Please vote for this!

https://one.workfront.com/s/idea/0870z000000XiHXAA0/detail

Discard Custom Messages over Versions of Proofs

You know how you can include a message on Proofs? But then it sticks with the proof throughout it's lifespan unless you select 'discard custom message'? I would like to suggest that those custom messages only send the first time.It causes confusion when a proof owner adds a message on the first version that is only applicable to that version, and then it carries through on version #2 because they forgot to take it off.

[Heather_Kulbacki]

Voting for this since in our use case I totally agree. I do know some people want that message to carry through to additional versions, so a checkbox to keep or discard would be ideal.