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

The DEV should not be responsible for quality of the issue description #296

Closed
t-izbassar opened this Issue Feb 22, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@t-izbassar

t-izbassar commented Feb 22, 2018

According to policy rules there are rules that talking about job description. But job description is what the issue reporter is doing, not the DEV. But if issue is not defined well - 0crat will punish the DEV for that (if QA will say that quality is bad), not the issue reporter and not the ARC or PO who approved issue as bug.

I don't see logic behind that. I'm just happen to be a DEV assigned to the task. Why I am who punished who the low quality of the issue itself?

I expect that ARC should be punished who accepting those kind of issues. When issue come up to DEV it should be already well defined and specific. Also, the issue reporter should be punished, if ARC rejects the issue and ARC should be rewarded (+5) for that action. As he is wasting time to read the issue and to understand whether it makes sense or not.

@0crat

This comment has been minimized.

Show comment
Hide comment
@0crat

0crat Feb 22, 2018

Collaborator

@yegor256/z please, pay attention to this issue

Collaborator

0crat commented Feb 22, 2018

@yegor256/z please, pay attention to this issue

@yegor256

This comment has been minimized.

Show comment
Hide comment
@yegor256

yegor256 Feb 22, 2018

Member

@t-izbassar you should not start working with the job, if the description is not correct. Just demand the author of the ticket to formulate it correctly.

Member

yegor256 commented Feb 22, 2018

@t-izbassar you should not start working with the job, if the description is not correct. Just demand the author of the ticket to formulate it correctly.

@yegor256 yegor256 closed this Feb 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment