[MGNLUI-6098] Statuses Showing On Content In Public Instances Should Be Hidden Created: 29/Jul/20 Updated: 10/May/23 Resolved: 07/Feb/22 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2.11 |
| Fix Version/s: | 6.2.17 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Julian Nodarse | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | VN-Testing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 3d 6.5h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Sprint: | UI Maintenance 4, Nucleus 3 | ||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||
| Description |
Current situationPublic instances show the status column. It doesn't make any sense, only When you log in to a public instance, you can see that content has an activation status symbol. It can be confusing for users to see this and try to make sense of why the statuses are there if unpublished content should not be present in public instances to begin with. These symbols show either red or green which does not make sense on content in a public instance. The status symbols should only be applicable to the author instance to indicate if something is published or not. Desired situationRemove the status column in the public instances. Keep consistent across apps.
|
| Comments |
| Comment by Roman Kovařík [ 03/Dec/21 ] |
|
Estimated: PoC. Let's try to just hide the content on public in the column's `ValueProvider` (not whole column) -> quickfix. |
| Comment by Quach Hao Thien [ 12/Jan/22 ] |
|
This ticket should be considered as improvement, and we will come back to it later after maintenance mode |