No, No You're definitely the Crowd we like to target .
we only report those Cases where users are blindly creating posts without checking for duplicates. yours is an honest mistake :D
Is there anything i can help you with ?
You are viewing a single comment's thread from:
Hi @sachincool. thank you for the replay. it helpes :-)
I have posted the issue post on the Github repository Github Issue as you suggested.
I do have a couple of question though. I tried to find the answers on steemit and utopion.io but was't able to get the clear idea. so if you can help i would really appreciate a lot.
Standard response time of the approval for bug-hunting is 48 hours so what will happen if 2 or more persons posts the same bug ? I wonder that in this case quality description of the bug counts. but still if you can please clarify more
going with same above scenario if one proper bug gets approved then will the second one will be marked as a duplicate ? Because technically until the bug is approved there is no duplicate and therefore it can not be marked as a duplicate.
Suppose i have posted bug and before bug gets approved and withing 48 hours bug gets resolved by developers then will it be consider as a genuine bug or it will be marked as a Not able to reproduce ?
If bug is genuine but it's reporting method hasn't followed the utopion rules then it will be rejected and bug reporter will be asked to correct it and submit it again.In this case what if someone adds a same bug but with proper instructions and following all the rules ? What will be outcome in this scenario ?
Same way if reporter is asked to edit the bug and submit it again then does 48 hours waiting window still apply ? or approval of the bug comes immediately.
I am sorry for the long list of questions. i could have asked you on discord but in this way someone new like me can find a way around bug hunting just by reading this and not have to ask same thing on discord , thus reducing the effort of future explaining.
Sorry for the delayed replay and long comment :-) I
Thanks,
Pritesh