[CFGUI-74] Action to reload the problems in the Problems view Created: 22/Mar/18 Updated: 25/Mar/22 Resolved: 25/Mar/22 |
|
| Status: | Closed |
| Project: | Definitions App |
| Component/s: | None |
| Affects Version/s: | 1.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Epic Link: | LD improvements | ||||||||||||||||||||
| Description |
|
The problems view can only be refreshed to show the latest state by switching subapps to the definitions subapp and back. It should be easy, clear, and one click away to reload the contents. (Note, a browser refresh also does not show the latest problems state.) The common usecase is that a developer is working to remove the problems in thier project. They have this view open and they fix code or config elsewhere - then they want to check again if the problem is fixed. The configured view should stay the same when the contents are reloaded so that a developer does not loose their place - ie same filters and same scroll-location. |
| Comments |
| Comment by Antti Hietala [ 20/Apr/18 ] |
|
A refresh view action could be useful also in other apps, not only in Definitions app. Should we provide it as a configurable action everywhere? Consider also |
| Comment by Christopher Zimmermann [ 23/Apr/18 ] |
|
I heartily agree that we should consider adding in other places. However I think it will be a fair amount of work to analyze and implement. I think its important that we address it specifically here in the problems view as soon as possible though, because its a primary function in the task in this app. (Fix problem, check again in definitions app) (This is also why I split |
| Comment by Christopher Zimmermann [ 23/Apr/18 ] |
|
Also, push support would be even better, but again do not want to delay this ticket. |
| Comment by Christopher Zimmermann [ 01/Apr/19 ] |
|
After discussing with Roman, this ticket is not obsolete. It could be applied directly to the port of the Definitions app though. |
| Comment by Roman Kovařík [ 08/Jun/21 ] |
|
Observation implemented in This ticket might be still valid for production instances. |
| Comment by Christopher Zimmermann [ 25/Mar/22 ] |
|
Feature implemented in linked tickets.. |