Summary
When a user submits feedback and attaches a screenshot, junior should attach that screenshot to the GitHub issue it opens. Currently screenshots shared in feedback are not propagated to the issue, losing visual context that could be useful for reproducing or understanding the reported problem.
Current behavior
Feedback is filed as a GitHub issue with text content, but any screenshots attached by the user are discarded and not included in the issue body or as attachments.
Gap
Screenshots often carry essential context (e.g. truncated UI, error states, unexpected layouts) that is difficult to convey in text. Dropping them reduces the usefulness of filed issues and forces the user to manually re-attach them if they want that context preserved.
Recommendation
When opening a GitHub issue from user feedback that includes one or more screenshots, embed the images inline in the issue body (via markdown image references or as linked uploads). If GitHub's API doesn't support direct binary upload via gh issue create, upload to a public-accessible store (e.g. GitHub release assets or similar) and reference the URL in the body.
Action taken on behalf of Michael Warkentin.
Summary
When a user submits feedback and attaches a screenshot, junior should attach that screenshot to the GitHub issue it opens. Currently screenshots shared in feedback are not propagated to the issue, losing visual context that could be useful for reproducing or understanding the reported problem.
Current behavior
Feedback is filed as a GitHub issue with text content, but any screenshots attached by the user are discarded and not included in the issue body or as attachments.
Gap
Screenshots often carry essential context (e.g. truncated UI, error states, unexpected layouts) that is difficult to convey in text. Dropping them reduces the usefulness of filed issues and forces the user to manually re-attach them if they want that context preserved.
Recommendation
When opening a GitHub issue from user feedback that includes one or more screenshots, embed the images inline in the issue body (via markdown image references or as linked uploads). If GitHub's API doesn't support direct binary upload via
gh issue create, upload to a public-accessible store (e.g. GitHub release assets or similar) and reference the URL in the body.Action taken on behalf of Michael Warkentin.