Defect #32322
changes made to filter/column/groupby is not saved to session cookie
Status: | Needs feedback | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Issues filter | |||
Target version: | - | |||
Resolution: | Affected version: | 4.0.4 |
Description
changes made to filter/column/groupby is not saved to session cookie, after the browser is closed and restarted, the settings recovered to default values.
Related issues
History
#1
Updated by Marius BALTEANU over 3 years ago
- Status changed from New to Needs feedback
On which tab do you refer? The filter options are saved in the session only for issues, for time entries not (you can see why #24581#note-2).
#2
Updated by Marius BALTEANU over 3 years ago
- Related to Feature #24581: Save spent time filters in session in order to have the same behaviour as for issue filters added
#3
Updated by Taine Woo about 3 years ago
Marius BALTEANU wrote:
On which tab do you refer? The filter options are saved in the session only for issues, for time entries not (you can see why #24581#note-2).
Hi Marius,
yes i refer to issues. Users change the columns and apply, and then close the browser, the columns will be reset to default values from Administration-Settings-IssueTracking, while user session is not expired.
#4
Updated by Taine Woo almost 3 years ago
Marius BALTEANU wrote:
On which tab do you refer? The filter options are saved in the session only for issues, for time entries not (you can see why #24581#note-2).
Method to reproduce:
1. Show "Issues" of project A, and make some changes (such as sort/columns);
2. Switch to project B, you will find the default setting value for columns and sort of the site is loaded.
3. Switch back to project A, changes made by step 1 is lost, settings for columns or sort is set to site default too.