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

Time to answer is not calculated, indicated as None for all issues #188

Closed
Piedone opened this issue Jan 10, 2024 · 2 comments
Closed

Time to answer is not calculated, indicated as None for all issues #188

Piedone opened this issue Jan 10, 2024 · 2 comments

Comments

@Piedone
Copy link

Piedone commented Jan 10, 2024

I've used the action to calculate repo:OrchardCMS/OrchardCore is:issue created:2023-12-01..2023-12-31 -reason:"not planned" but the "Time to answer" column is None for every issue:

image

Note how the aggregated metrics at the top also show "Time to answer" as None for all three columns.

Almost every issue listed here had an answer (from a core contributor) within the same time period.

The same issue exists for PRs too. There BTW an approval should also be considered an answer I'd say.

@zkoppert
Copy link
Member

Hi! Time to answer is only applicable to discussions since a post in a comment can be marked as "answered". If you would like, you can hide the time to answer stat with the HIDE_TIME_TO_ANSWER variable with more details in the configuration section of the README.

@Piedone
Copy link
Author

Piedone commented Jan 11, 2024

Thank you for your quick reply! Ah, I see, I missed that. Then all is good, thank you. Works great:

@Piedone Piedone closed this as not planned Won't fix, can't repro, duplicate, stale Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants