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

QA rule - the impediment request should clarify what exactly the impediment is #300

Closed
t-izbassar opened this Issue Feb 23, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@t-izbassar

t-izbassar commented Feb 23, 2018

When DEV or CR request for the impediment - it is slowing down the whole process. The fact is that to register impediment you don't need to clarify what exactly you are waiting for. I feel like this decreases the quality, as it is not clear what are the dependencies between tasks and in which order they should be finished.

Thus, there should be a QA rule that sounds something like this:

Impediment registered in the ticket has clear link on connected issues.

@0crat

This comment has been minimized.

Show comment
Hide comment
@0crat

0crat Feb 23, 2018

Collaborator

@yegor256/z please, pay attention to this issue

Collaborator

0crat commented Feb 23, 2018

@yegor256/z please, pay attention to this issue

@yegor256

This comment has been minimized.

Show comment
Hide comment
@yegor256

yegor256 Feb 26, 2018

Member

@t-izbassar sounds right. In the future, please report policy changes/bugs to this repo: https://github.com/zerocracy/zerocracy.github.io

Member

yegor256 commented Feb 26, 2018

@t-izbassar sounds right. In the future, please report policy changes/bugs to this repo: https://github.com/zerocracy/zerocracy.github.io

@yegor256

This comment has been minimized.

Show comment
Hide comment
@yegor256
Member

yegor256 commented Feb 26, 2018

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