[MAGNOLIA-6816] Provide availability rule for locked node case Created: 12/Oct/16  Updated: 16/Mar/21  Resolved: 16/Mar/21

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.5
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-6560 Isolation level of MarkNodeAsDeleted ... Closed
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)
Story Points: 5

 Description   

Since MAGNOLIA-6560, there is a possibility of having a node locked. This would lead to confusion from a user point of view since the actions will be available but node is locked therefore activated action would fail. Hence, we should be providing availability rule for those cases and have it installed by default to regarding actions.


Generated at Mon Feb 12 04:18:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.