brave/brave-browser

Make it easier to copy the version, revision, and OS when reporting an issue

Open

#6,916 opened on Nov 14, 2019

View on GitHub
 (21 comments) (0 reactions) (0 assignees)JavaScript (2,164 forks)batch import
feature-requestgood first issuepriority/P4support

Repository metrics

Stars
 (16,194 stars)
PR merge metrics
 (Avg merge 4h 38m) (19 merged PRs in 30d)

Description

Description

Suggestion: When reporting an issue, you're asked (for production builds) to copy the Brave, Revision, and OS information from brave://version/ into the issue, It's surprisingly fiddly to do that with the current layout of the version page. I suggest adding a [Copy] button or similar that grabs it to the clipboard in a form that can be easily pasted into the issue.

Steps to Reproduce

Actual result:

Expected result:

Reproduces how often:

N/A, new feature suggestion

Brave version (brave://version info)

;-)

Brave | 1.0.0 Chromium: 78.0.3904.97 (Official Build) (64-bit)

Revision | 021b9028c246d820be17a10e5b393ee90f41375e-refs/branch-heads/3904@{#859}

OS | Linux

Version/Channel Information:

Other Additional Information:

N/A, new feature suggestion

Contributor guide

Research direction
Locate the brave://version page component and implement a copy to clipboard button for the version details.
Tech stack
javascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75