Provisioning Group Delete Nodes Workflow Confusing
Description
I was trying to delete a provisioning group today, and I dutifully click on "Delete Nodes" and I kept waiting for the node to go away. I wasn't thinking and forgot that I had to synchronize after hitting delete.
While definitely a user error, it seemed like the process could be improved. I talked to Matt and we came up with the following:
It is a bit dangerous to hit "Delete Nodes" and to immediately delete the requisition import file. We should pop up a "confirm" button before doing it (since it can't be undone). In that pop up we should also remind the user that they have to hit synchronize as well.
Environment
Operating System: All
Platform: PC
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
David Hustace February 7, 2011 at 8:53 AM
I think we should make new subdirectories for deleted requisitions and foreign source specifications.
Seth Leger February 3, 2011 at 4:25 PM
I've fixed the Javascript confirmation when you try to delete a provisioning group. This went into master for inclusion in 1.9.4. commit 6cb67e05bb681bf00ca5c41d4f9ba46885eb7a39
It sounds like the rest of this bug is basically to add a notice to the UI when "unsynchronized" changes are present in a given provisioning group.
I was trying to delete a provisioning group today, and I dutifully click on "Delete Nodes" and I kept waiting for the node to go away. I wasn't thinking and forgot that I had to synchronize after hitting delete.
While definitely a user error, it seemed like the process could be improved. I talked to Matt and we came up with the following:
It is a bit dangerous to hit "Delete Nodes" and to immediately delete the requisition import file. We should pop up a "confirm" button before doing it (since it can't be undone). In that pop up we should also remind the user that they have to hit synchronize as well.