Created attachment 765002 [details] Update button problem Description of problem: The modal dialog for viewing/updating task details doesn't disappear after clicking its "Update" button. Version-Release number of selected component (if applicable): jBPM console DR5 deployed on JBoss EAP 6.1 How reproducible: Always Steps to Reproduce: 1. Navigate to BPM > Tasks - Grid View (Advanced view) 2. Click "New Task" - just fill in some task name and click "Create" 3. Details for the newly created task (the magnifying glass icon) 4. Fill in some new values (e.g. Description, change priority etc.) 5. Scroll down and click "Update" Actual results: The Details window remains open. Even though task details ARE updated the change is not reflected in the GUI (you must close the modal dialog by "x" and then refresh the page) Expected results: After "Update" is clicked, the Modal dialog should disappear and the task details displayed in the Task list should be updated in the GUI. Additional info: See Screenshot
When I've created this tab, I didn't wanted to close the modal after the user updated the task details. The main reason is that usually the will want to move to another tab to do the work or to change more things. A notification is create when the task is updated. And the OnClose action of the modal should refresh the task list in the back when the modal is closed. If we all agree that the update button should close the modal I don't mind doing it. It's a 5 minutes change, but I originally designed it to not do that.
Mauricio, maybe it makes sense that the modal is not closed after update button is clicked (I don't know yet how exactly the gui will be used). However gui is NOT updated even after closing the modal. I made a short video reproducing the problem so you can see what I mean - I set new task priority, but then after clicking update and then closing the modal, the new priority is not reflected in the list. I tested with community Beta4 build.
Created attachment 767670 [details] Steps to reproduce - video
I will fix that in master and I will mark this issue as modified
Fixed in master
Verified with BPMS 6.0.0.ER2