[MGNLPER-68] Filter out results from apps that can't display the found node Created: 21/Nov/18 Updated: 21/Nov/18 Resolved: 21/Nov/18 |
|
| Status: | Closed |
| Project: | Periscope |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| 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)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Description |
|
Filter out results from apps that can't display the found node. To reproduce:
Issue: Configuration, Cookies and Site apps are displayed in results. Only the Configuration app has access to the found target node appLauncherLayout. The other two apps can only access a very narrow subtree elsewhere in the config workspace. Since the user has no way of navigating to the appLauncherLayout node in the Cookies and Site apps the results are misleading.
|