You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Exploratory] Chat - Markdown formatting inconsistent in description hint change log #98740
Pre-condition Have Workspace with Rules enabled , Have a expense
Go to staging.expensify.com
Go to workspace settings - category -Advertising- description hint
Enter cat and save
Again open description hint and enter catruns
Go to admin room and note the change log shown cat runs without markdown applied
Open the expense - description
Repeat steps 3 and 4
Note the system message for description shown with markdown applied
Expected Result:
Markdown formatting should be applied consistently in the admin room change-log system message, matching the formatting shown in the expense description system message.
Actual Result:
Markdown formatting is not applied in the admin room change-log system message. catruns is displayed as plain text (cat runs), while the corresponding expense description system message renders the Markdown formatting correctly.
changed the title [-][Exploratory] Chat-Markdown formatting inconsistent in description hint change log[/-][+][Exploratory] Chat - Markdown formatting inconsistent in description hint change log[/+]on Aug 17, 2026
Activity
applause-bot commentedon Aug 17, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/bb6ccf30f3739f7e00db404f24bc93f75ecc35eb6682807a2f1578707ce43487
[-][Exploratory] Chat-Markdown formatting inconsistent in description hint change log[/-][+][Exploratory] Chat - Markdown formatting inconsistent in description hint change log[/+]melvin-bot commentedon Oct 29, 2026
@applause-bot[bot], this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.