[MGNLCAMPU-59] Remove inconsistent behaviour for config nodes, add check for MarkAsReady action if in campaign are all not published ancestors Created: 17/Feb/17  Updated: 23/Aug/22

Status: Open
Project: Campaign Publisher
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Evzen Fochr Assignee: Unassigned
Resolution: Unresolved 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)
Date of First Response:
Epic Link: Campaign Publ. cleanup
Team: AuthorX

 Description   
  1. Remove inconsistent behavior - revert commit c8b4b8af91d1977e72e29e6e83416535c5e2df85
    this removes inconsistent behavior that allows publishing lvl3+ in config ws without checking if parents are published
  2. Add warning confirmation dialog to MarkAsReady action that warn user that there are still not published parent nodes that are not in campaign.


 Comments   
Comment by Jan Haderka [ 23/Mar/17 ]

lvl+3 subnodes - but lvl1 and lvl2 parents are ALWAYS published in config, otherwise instance would not work. Why the check then?

Generated at Sun Feb 11 23:57:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.