Content
View differences
Updated by Pavel Balashou over 2 years ago
The feature came up out of [https://community.openproject.org/wp/51853](https://community.openproject.org/wp/51853)
Describe the following bug report: [https://community.openproject.org/wp/51853.](https://community.openproject.org/wp/51853) inconsistentcy.
Inconsistencies:
1\. In `/cost_report` when filters are modified a user has to click `Apply` to save them in session. So, after reload Cost reporting uses the filters are not gone. In `/work_packages` when filters are modified it is reflected in the current page URI same filtering approaches as work packages.
**As** a query parameter right away.
2\. There is a difference in the behavior \[enter role of `Apply` button between `/cost_report` and `/cost_report/:id`. In the later case the filters are not saved to the session. So, after refresh they are gone.
The suggestion is to make `/cost_reports` behavior more aligned with `/work_packages` . A few examples: user\]
1\. Make filters bound to current page query parameters. Update it as soon as filter has been chosen by user. And update the display view as well. So, `Apply` button can be removed then. **I want to** \[enter objective\]
**so that** \[enter desired result\]
2\. Do not store filters in user's session and rely on saved in db queries. **Acceptance criteria**
3\. Move `Save` "diskette" and the top left corner and highlight it when filters are not aligned with saved in the database query. *
Describe
Inconsistencies:
1\. In `/cost_report` when filters are modified a user has to click `Apply` to save them in session. So, after reload
**As**
2\. There is a difference in the behavior
The suggestion is to make `/cost_reports` behavior more aligned with `/work_packages` . A few examples:
1\. Make filters bound to current page query parameters. Update it as soon as filter has been chosen by user. And update the display view as well. So, `Apply` button can be removed then.
**so that** \[enter desired result\]
2\. Do not store filters in user's session and rely on saved in db queries.
3\. Move `Save` "diskette" and the top left corner and highlight it when filters are not aligned with saved in the database query.