[MGNLUI-3622] Provide simple boolean logic for availability rules Created: 12/Oct/15 Updated: 11/Mar/21 Resolved: 11/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 1 |
| Labels: | to-specify | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Story Points: | 5 | ||||||||
| Description |
|
Proposed additions:
This simple improvement that would allow us:
|
| Comments |
| Comment by Roman Kovařík [ 12/Oct/15 ] |
|
Don't you want to go with voters like in |
| Comment by Michael Mühlebach [ 12/Nov/15 ] |
|
Evaluate this vs using Voters which is currently done for the travel demo users. |
| Comment by Mikaël Geljić [ 12/Nov/15 ] |
|
Voter-based availability was our first proposal back during development of 5.3, but it was demoted for various reasons... Definitely worth re-evaluating though. |
| Comment by Roman Kovařík [ 11/Mar/21 ] |
|
Implemented in M6.2 as negate property of availability rules. |