[#SAK-8026] Legacy tools should not save state.

Sakai

Legacy tools should not save state.

Created: 08-Feb-2006 18:10 Updated: 09-Feb-2007 11:26

Component/s:

Global

Affects Version/s:

2.2.0

Issue Links:

Duplicate

This issue duplicates:

~~SAK-8115~~ Sakai Saving State - Moving between tools and within pages of a tool should behave conistently for users.

Description

« Hide

When someone enters information into a form the state should not be saved when they go to another tool.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Kristol Hancock added a comment - 13-Feb-2006 21:52

Assigning to Jordi for review.

[ Permlink | « Hide ]

Unitat Docencia Virtual UDL added a comment - 14-Feb-2006 04:45

This would disable one of SAKAI's features, and can be overriden by the user by clicking the "reset" button located on each tool.

[ Permlink | « Hide ]

Mara Hancock added a comment - 14-Feb-2006 19:31

This is not the role of clumping and clustering activity. Closing should only happen when we have been able to combine (through clumping) requirements. How or whether or not a requirement is delivered on is decided during the voting and resource allocation process.

[ Permlink | « Hide ]

Unitat Docencia Virtual UDL added a comment - 27-Feb-2006 02:40

Ready for voting

[ Permlink | « Hide ]

Charles Severance added a comment - 15-Sep-2006 03:25

This will be a provisional feature in 2.3

14687 and 14596

[ Permlink | « Hide ]

Peter A. Knoop added a comment - 15-Sep-2006 06:00

See REQ-37 for progress going forward.