[CONTEDIT-427] DOC: Warning message when edit incompatible i18n stories structure Created: 29/Sep/21  Updated: 11/Oct/21  Resolved: 11/Oct/21

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: None
Fix Version/s: 2.1

Type: Improvement Priority: Neutral
Reporter: Laura Delnevo Assignee: Martin Drápela
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen+Shot+2021-09-29+at+14.39.55.png    
Issue Links:
Cloners
clones CONTEDIT-422 Improve warning message when edit inc... 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)
Date of First Response:
Epic Link: i18n Stories App
Sprint: Content Mngmt 14
Story Points: 1

 Description   

Follow up from CONTEDIT-422

Hey team, I found the newly proposed text for 422 , thx @Martin for re-writing the notification message


A couple of suggestions here, there could be addressed in documentation maybe
---- * add the screenshot of the notification to documentation

  • explain what ‘custom’ field is and why/how it’s used
  • explain what impact it has to be set as true/false - e.g. I can’t edit blocks unless it’s set to false (just making this up as an example)

wdyt?


I am thinking from the user point of view, either author or developer who are new to Stories or i18n. They read the message but they might not know why the ‘custom’ field is relevant to them or what impact it has
 


Generated at Mon Feb 12 00:20:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.