Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reporting-Errors Docs are confusing #48

Open
capndave opened this issue Sep 4, 2020 · 1 comment
Open

Reporting-Errors Docs are confusing #48

capndave opened this issue Sep 4, 2020 · 1 comment
Assignees
Labels
bug Something isn't working doc Documentation purposes
Projects
Milestone

Comments

@capndave
Copy link

capndave commented Sep 4, 2020

Describe the bug
Text is confusing

To Reproduce

  1. Go to https://docs.trefle.io/docs/guides/reporting-errors
  2. At bottom of page, look at text under "Testing"
  3. Read it. The second sentence reads "They will be not reviewed, and automatically rejected after some time."

Expected behavior
A clear explanation of whether testing a report will be reviewed (by treflehq) and whether and under what conditions the report will be accepted or rejected

Additional context
Reading this, it sounds to me like if you test then your report will not be reviewed (by a human) and will be automatically rejected (by a machine). That's not the case, is it?

@capndave capndave added the bug Something isn't working label Sep 4, 2020
@lambda2
Copy link
Member

lambda2 commented Sep 8, 2020

Hey @capndave, copy that, we'll add clearer explanations.
About the report, it will be rejected after some time by a task that periodically runs over all reports matching "TEST".

@lambda2 lambda2 added this to Needs triage in Issues via automation Sep 9, 2020
@lambda2 lambda2 added this to the 1.6.1 milestone Sep 9, 2020
@lambda2 lambda2 added the doc Documentation purposes label Sep 9, 2020
@lambda2 lambda2 moved this from Needs triage to Low priority in Issues Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working doc Documentation purposes
Projects
Issues
  
Low priority
Development

No branches or pull requests

2 participants