Content
View differences
Updated by Parimal Satyal over 2 years ago
**As** a user
**I want to** differentiate the "Preview not available" information message easily from user provided text
**so that** I am not confused
In case the text (project description, status description or long text custom fields) contain tables, macros or images, instead of attempting to display the elements, a "Preview not available" placeholder is currently displayed:
<img class="op-uc-image op-uc-image_inline" style="width:428px;" src="/api/v3/attachments/93167/content">
### **Acceptance criteria**
* Have the "Expand" button right aligned when visible
* Visually differentiate the "Preview not available" text from user provided by displaying in:
* a lighter shade of grey
* in italics
### **Visual**
**Focus on the status description column:**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/93174/content"> provided, abbreviated content \[TBD\]
**I want to** differentiate the "Preview not available" information message easily from user provided text
**so that** I am not confused
In case the text (project description, status description or long text custom fields) contain tables, macros or images, instead of attempting to display the elements, a "Preview not available" placeholder is currently displayed:
<img class="op-uc-image op-uc-image_inline" style="width:428px;" src="/api/v3/attachments/93167/content">
### **Acceptance criteria**
* Have the "Expand" button right aligned when visible
* Visually differentiate the "Preview not available" text from user provided by displaying in:
* a lighter shade of grey
* in italics
### **Visual**
**Focus on the status description column:**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/93174/content">