Skip to content

Conversation

@mtopo27
Copy link
Contributor

@mtopo27 mtopo27 commented Nov 25, 2025

image

copy feedback as markdown to make it easier to dump into LLM.

For reviewers, talked this over with @jas-kas and see it as a low-hanging fruit addition that could be helpful for addressing individual feedback items

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 25, 2025
@mtopo27 mtopo27 force-pushed the mtopo27/add-copy-markdown-to-user-feedback branch from 9bd675c to 0725ea7 Compare November 25, 2025 21:45
@mtopo27 mtopo27 changed the base branch from master to mtopo27/add-app-contexts-to-event-type November 25, 2025 21:45
Base automatically changed from mtopo27/add-app-contexts-to-event-type to master November 25, 2025 22:19
@mtopo27 mtopo27 force-pushed the mtopo27/add-copy-markdown-to-user-feedback branch from 0725ea7 to 9635c0b Compare November 25, 2025 22:20
@mtopo27 mtopo27 marked this pull request as ready for review November 25, 2025 22:21
@mtopo27 mtopo27 requested a review from a team as a code owner November 25, 2025 22:21
Comment on lines 71 to 75
trackAnalytics('feedback.copy-feedback-as-markdown', {
organization,
feedback_id: feedbackItem.id,
project_slug: feedbackItem.project?.slug,
});

This comment was marked as outdated.

const markdown = [
'# User Feedback',
'',
`**Summary:** ${summary}`,
Copy link
Member

@ryan953 ryan953 Nov 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what if we just skipped this line if there's no summary provided?

If an org turns off their AI stuff, or is on-prem and doesn't have Seer at all then it'll be really annoying to see **Summary:** No summary provided every time

Comment on lines +62 to +68
...(sourceLines.length
? [
'',
'## Source (_where user was when feedback was sent_)',
sourceLines.join('\n'),
]
: []),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we also include tags? I feel like those are useful to us internally, we use them almost everywhere now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at a few examples, I think many of the tags are superfluous to implementing a feedback fix/ticket. Going to merge initial version without and we can easily add in if we fill they'd be a benefit

});

copy(markdown, {
successMessage: t('Copied feedback summary'),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
successMessage: t('Copied feedback summary'),
successMessage: t('Copied feedback'),

Copy link
Member

@ryan953 ryan953 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

iteration suggestions, but overall cool

@mtopo27 mtopo27 merged commit e195c19 into master Dec 1, 2025
48 checks passed
@mtopo27 mtopo27 deleted the mtopo27/add-copy-markdown-to-user-feedback branch December 1, 2025 13:52
jerryzhou196 pushed a commit that referenced this pull request Dec 1, 2025
<img width="1800" height="130" alt="image"
src="https://github.com/user-attachments/assets/495ea37a-8333-48d3-8588-061557aa248e"
/>

copy feedback as markdown to make it easier to dump into LLM. 

For reviewers, talked this over with @jas-kas and see it as a
low-hanging fruit addition that could be helpful for addressing
individual feedback items
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants