Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

stable

Clone or download

Read-only

fix: Markdown value not interpreted in Tracker table report

Download Browse

This closes request #29248 Markdown value not interpreted in Tracker table report When adding a text field as a column in a Tracker table report, if an artifact has this text field value format is set to Markdown, then the value is not interpreted in the report. If the value is set to HTML, then the value is interpreted. We have to be consistent and both values must be interpreted. How to test ----------- * Have an artifact with a Markdown value in a text field * Go to a table report of the tracker of the artifact * Add this field as a column of this table => Markdown content must be interpreted Change-Id: Ie9ef7d251f2510a6d416d3d77aa7a123b6c18dd4 Note: there is some technical changes in docblock to fix psalm errors.

+12 −7
Yannis ROSSETTO (rossettoy) 2022-10-24 15:00
Yannis ROSSETTO (rossettoy) 2022-10-24 15:00
0c45871dc17e68670660600ae34e635526c97e6e
1fdc8d21abe276c4f609da497cfccb9ec193bfad
git #tuleap/stable/0c45871dc17e68670660600ae34e635526c97e6e

Modified Files

Side by side diff
Inline diff
Name
M plugins/testmanagement/include/TestManagement/Step/Definition/Field/StepDefinition.php +0 −3 Go to diff View file
M plugins/testmanagement/include/TestManagement/Step/Execution/Field/StepExecution.php +0 −3 Go to diff View file
M plugins/tracker/include/Tracker/FormElement/Tracker_FormElement_Field_Text.php +10 −0 Go to diff View file
M plugins/tracker/include/Tracker/Tracker_Report_Field.class.php +2 −1 Go to diff View file