Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 498a178

Browse files
committed
awarding only with swag doesn't stop bounty timer
1 parent 99170e9 commit 498a178

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/programs/response-target-metrics.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Response Efficiency Metric | Details
1010
---- | -------
1111
Time to first response | The elapsed time from report creation to the first public activity on a report. The first public activity includes adding a public comment, changing the report state, or changing the report severity.
1212
Time to triage | The elapsed time from when a report is created to when a report is changed to a triaged state. A report can skip the triaged state and move directly to a closed state (e.g. resolved).
13-
Time to bounty | *(Bounty programs only)* The elapsed time from when a report is triaged to when a bounty is paid. Only reports that are eligible for a bounty will be tracked as part of this metric. The time to bounty timer will run until the report is either marked as ineligible or closed as a state where it’s not normal to award a bounty (e.g. spam).
13+
Time to bounty | *(Bounty programs only)* The elapsed time from when a report is triaged to when a bounty is paid. Only reports that are eligible for a bounty will be tracked as part of this metric. The time to bounty timer will run until the report is either marked as ineligible or closed as a state where it’s not normal to award a bounty (e.g. spam).<br><br><i>Awarding swag in lieu of a bounty won't stop the timer. If you only award a report with swag, you must mark the report as ineligible for bounty to stop the timer</i>.
1414
Time to resolution | The elapsed time between report triaged and report closed. These five closed report states will stop the timer: resolved, informative, not applicable, duplicate, and spam.
1515

1616
All response target times are tracked and reported in business days. Business days are defined to be:
@@ -25,13 +25,13 @@ Some response target definitions to keep in mind when configuring your program's
2525
Term | Detail
2626
----- | ------
2727
Response Standard | The maximum acceptable response times as defined by HackerOne. These standards only apply for time to first response and time to triage. HackerOne may temporarily pause new report submissions for programs with reports that don't meet the response standards. When these programs address the reports violating the response standards, report submissions will automatically resume.
28-
Target | Goal response times set by an individual program. Performance against targets are displayed internally in the Inbox and Program Health dashboard. Program targets can't be set to exceed the response standards.
29-
Recommended | The default setting for all new programs and HackerOne's suggested setting for best practice.
28+
Target | Goal response times set by an individual program. Performance against targets are displayed internally in the Inbox and Program Health dashboard. Program targets can't be set to exceed the response standards.
29+
Recommended | The default setting for all new programs and HackerOne's suggested setting for best practice.
3030

3131
### Healthy Response Target Times
3232
HackerOne recommends your program to follow the following response target times to ensure a healthy program:
3333

34-
Response Efficiency Metric | Recommended | Response Standard | Target
34+
Response Efficiency Metric | Recommended | Response Standard | Target
3535
-------- | ----------- | ----------------- | -------
3636
Time to first response | 1 day | 5 days | Customized
3737
Time to triage | 2 days | 10 days | Customized

0 commit comments

Comments
 (0)