History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SAK-11838
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Venkatesh Subramanian
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Sakai

"Submit for Evaluation" button missing while Previewing a Matrix

Created: 07-Oct-2007 23:07   Updated: 23-Oct-2008 06:29
Component/s: OSP: Wizards - Matrix
Affects Version/s: 2.5.0
Fix Version/s: 2.5.0

Time Tracking:
Not Specified

Environment:
Windows Vista Home, Mozilla Firefox 2.0.0.7
Sakai Instance: http://qa2-osp.sakaiproject.org:8084/osp-portal

2.4.x Status: None
2.5.x Status: None
2.6.x Status: None


 Description  « Hide
Steps to reproduce the bug:

1) Create a matrix.
2) Click on the preview button.
3) Click on the Matrix name, and then a cell.
4) Enter data into the cell.
5) "Submit for Evaluation confirmation" button is missing, so that the cell can be submitted for evaluation.
6) This happens only during the "previewing" phase, once the matrix is published, the button is visible.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Beth Kirschner - 18-Oct-2007 07:07
This appears to be resolved in the sakai_2-5-0_QA_009_GMT tag (unable to reproduce).

Megan May - 22-Oct-2007 11:29
changing fix version based off of Beth comments

Neha Saxena - 15-Mar-2008 13:17
For 2.5.x and IE7 : I followed the following steps

1) Created a matrix.
2) Clicked on the preview button.
3) Clicked on the Matrix name, and then a cell.
4) Enter data into the cell.
5) No "Submit for Evaluation confirmation" was shown
6) Now published the matrix
7) I still did not find the submit for evaluation button

Beth Kirschner - 17-Mar-2008 05:58
Nexha -- I'll send an email separately on this -- the matrix works as expected when I use on qa2-osp server.

Filter Maintainer - 08-Aug-2008 06:03
2.5.0 QA has been completed. Unfortunately, there were not resources available to specifically test this issue. If you find this to still be a problem in the latest release (at this point 2.5.2), please reopen the JIRA and add the latest affects version.