[CFGUI-56] Refresh problems after they're fixed Created: 07/Nov/16  Updated: 09/Nov/16  Resolved: 09/Nov/16

Status: Closed
Project: Definitions App
Component/s: None
Affects Version/s: 1.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Problems view is great; jumping to definition and then to JCR config app makes it trivial to fix common mistakes. Sad thing is that problems do not go away after fixing them.

We should have an idea how to flush/refresh those TransformationProblems when definitions are re-registered.

Refreshing when the app is restarted could be an intermediate step; currently it requires a server restart.



 Comments   
Comment by Mikaël Geljić [ 09/Nov/16 ]

Totally my bad, problem I chose was the availability "double-node" under security-app's addFolder action. I fixed it in users subapp; remaining problems I observed were coming from groups/roles subapps. Closing it as "reporter is blind".

Generated at Mon Feb 12 00:44:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.