[MGNLPN-47] Missing i18n keys in segmentation app Created: 24/Mar/14  Updated: 25/Mar/14  Resolved: 24/Mar/14

Status: Closed
Project: Magnolia Personalization
Component/s: Segmentation App
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Won't Fix Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MGNLPN-38 Streamline Content Apps (Segmentation... 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Personalisation
Sprint: 5.3 Sprint 4

 Description   

segmentation.browser.actions.activateSegment.successMessage
segmentation.browser.actions.activateSegment.failureMessage

segmentation.browser.actions.activateFolder.successMessage
segmentation.browser.actions.activateFolder.failureMessage



 Comments   
Comment by Roman Kovařík [ 24/Mar/14 ]

Using of standard action names as part of MGNLPN-38 should solve this issue.

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