# Remediation Tracker tickets that tell the whole story

**URL:** <https://discuss.dradis.com/t/remediation-tracker-tickets-that-tell-the-whole-story/1033>\
**Category:** Announcements\
**Created:** [November 6, 2026, 5:43pm UTC](https://discuss.dradis.com/t/remediation-tracker-tickets-that-tell-the-whole-story/1033 "2026-11-06T17:43:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![MattBudz](https://yyz1.discourse-cdn.com/flex035/user_avatar/discuss.dradis.com/mattbudz/32/203_2.png) [@MattBudz](https://discuss.dradis.com/u/MattBudz)\
**Post date:** [November 6, 2026, 5:43pm UTC](https://discuss.dradis.com/t/remediation-tracker-tickets-that-tell-the-whole-story/1033/1 "2026-11-06T17:43:38Z")

</div>

Liquid makes your Issues smarter. Until now, that stopped at the Remediation Tracker: tickets were created from the Issue’s source content, so the developer opening one saw your Liquid raw instead of evaluated.

Now the ticket gets the finished text. In this example, the project name and the “2 affected locations” both come from Liquid in the original Issue:

![rt-send](https://canada1.discourse-cdn.com/flex035/uploads/dradisframework/original/1X/2db62d21cd3c5a6499cec00c8f8417318992817b.gif)

Look at the bottom of that ticket too. Every ticket you send from an Issue now gets its own **Project** , **Issue** , and **Evidence** fields, with readable links instead of a long URL. Evidence is a list with one link per affected location, so anyone with access to the project is one click away from the proof.

Both changes happen on their own. Open an Issue, send it to **Remediation Tracker** , and check the ticket before you create it. This ships in Dradis Pro 5.5.0.

What else would make these tickets more useful for the people fixing the findings? Let us know below.