In 15.5 it is much too easy to accidently mark a task 100% complete and remove all ETC. It is done by clicking in the circle just to the left of the task name. As it works this is not usable for our company.
Any plans to address this in the future?
To add to this, if there are actual hours posted on the task you will not be able to add ETC back. You have to do it in Classic on the assignments.
Thanks Liz. Should I open a support case on this? It may not technically be a defect (IE it is working as coded). But with the current design it is much too risky to roll out the new UX at all. One accidental click and it is back to the Audit trail to rebuild the task! This is assuming you are auditing ETC.
What is the best way to get this to Product Management to get their input/feedback to verify if it is planned to be addressed in future release?
Tend to agree that setting complete is easy and maybe usable, but wiping ETC is just too much. The design specs should be questioned and tested for user acceptance.
I recently worked in a Support case about a similar issue about deleting tasks without confirmation. As you probably already know, this cannot be reported as a defect as it is behaving exactly as intended. You are suggesting an enhancement/change over the current design, so in order to do that, you can use the innovation process: New Customer Innovation Process for Clarity PPM.
As Customer votes is one of the most important factors when deciding which Ideas are being taken into consideration (although not the only one), try to check first if there is any existing idea to add your votes to, and if you open a new one, it could be good that you share it in the Community, so that other people that finds this thread can also go and vote for your idea.
Hope this helps.
Yes, I have submitted an idea. This is not a defect, it is working as they coded it. I also reached out directly to the Product Management on this. I do not feel people should have to use their chips to vote to fix a poor design decision. This should be fixed in a future patch.
I do think that anything should be such that entering something in the screen or just one click (without any prior selection) deletes something in the database. Even further no-no is that something which is not currently displayed.
The Sustaining Engineering team is now investigating this as a defect that they are looking into fixing. Here's the KB with the details: https://comm.support.ca.com/kb/phase-task-list-tool-tip-in-new-ux-causes-tasks-to-be-prematurely-marked-completed/kb000127761. We'll update the KB with updates on this one.
That is good as it addresses one part of the problem.
The other part it setting the ETC to zero when marking the task complete.
Just wondering if that behavior (for all the assignments of the task) is stated in the documentation.
Retrieving data ...