Sync PR changelog back to linked Featurebase issue

Add automatic synchronization of developer changelog information from Git back to the related Featurebase issue.

Git tasks linked to Featurebase contain the original Featurebase post URL at the bottom of the issue description.

Example:

This issue is linked to our feedback platform. For more details and updates, please visit [this link]
(https://enderturing.featurebase.app/p/add-csi-as-a-separate-column-in-report-export).

This URL should be used to identify the Featurebase issue associated with the Git task.

Required Flow

When a PR linked to a Git task is merged:

Identify the Git task related to the PR.
Read the Featurebase URL from the Git task description.
Take the changelog prepared by the developer for the PR.
Add the changelog to the linked Featurebase post as an update/comment.

Expected Behavior

Expected flow:

Featurebase post → Git task → PR → Changelog → Featurebase post

The Featurebase URL stored in the Git task should be used as the source of truth for identifying the related Featurebase issue.

Acceptance Criteria

The Featurebase URL is detected from the Git task linked to the PR.
After the PR is merged, its changelog is added to the linked Featurebase post.
If no Featurebase URL is present in the Git task, no Featurebase update is created.

Completed1

John

Team•

Sep 22

Product update from PR #6168.

Enhancement: Feedback Requests Now Get Automatic Progress Updates

When a feature you requested ships, the update is posted directly to your original feedback post — and the support link now points to our dedicated help portal.

Benefits

Get notified on your own feedback post when the request you submitted is delivered, without having to check back manually.
Read a plain-language summary of what changed, written for users rather than developers.
Close the loop between "I asked for this" and "this is live" — your feedback visibly turns into product changes.
Reach support through a cleaner, easier-to-remember address at support.enderturing.com.

Who Benefits

QA Managers: See directly on the feedback board when the scoring or reporting improvements you requested become available, so you can plan rollouts to your team.
Team Leads: Track which of your team's suggestions have shipped without chasing status in separate channels.
Admins: Know when requested configuration or integration changes are live before users start asking.
All users who submit feedback: Receive a visible confirmation that a request was implemented, attached to the original post.

Before & After

Before	After
Feedback posts stayed silent after submission; you had to ask or watch release notes to learn whether a request shipped	Each delivered request receives an update comment on the original feedback post
Product updates lived only in release notes, disconnected from the request that prompted them	The update appears exactly where the conversation started
Support tickets opened via a third-party-branded URL	Support opens at support.enderturing.com

Time & Effort Saved

Removes the need to manually follow up on submitted feedback — status arrives on the post itself.
Cuts repeated "is this done yet?" exchanges with your account or support contact.

Use Cases

A QA Manager requests an additional column in report exports; months later the update lands as a comment on that exact feedback post, and the whole team following it is informed at once.
A Team Lead reviewing the feedback board can scan which submitted ideas are now shipped versus still planned.
An Admin bookmarks support.enderturing.com as the single entry point for raising tickets.

How to Use

No setup required. Visit your post on the Ender Turing feedback board — delivered requests now carry a product update comment describing what shipped. Support tickets are now opened at support.enderturing.com, and existing links continue to route you there.

PR: #6168