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

_after.groovy:28-33: The ticket should be removed from... #599

Closed
0pdd opened this issue Feb 19, 2018 · 5 comments
Closed

_after.groovy:28-33: The ticket should be removed from... #599

0pdd opened this issue Feb 19, 2018 · 5 comments

Comments

@0pdd
Copy link
Collaborator

0pdd commented Feb 19, 2018

The puzzle 539-4e7a4000 from #539 has to be resolved:

* @todo #539:30min The ticket should be removed from WBS and performer
* should receive payment and awards only if ticket was closed by the reporter,
* ARC or PO. In other cases we should say "sorry, we won't pay".
* So let's provide who close an issue in claim params in `RbOnClose`
* and check it in 'Close job' and 'Remove job from WBS' scripts, then
* commented tests will be worked. Also policy have to be updated.

The puzzle was created by g4s8 on 15-Feb-18.

Estimate: 30 minutes, role: IMP.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0crat
Copy link
Collaborator

0crat commented Feb 19, 2018

@yegor256/z please, pay attention to this issue

@0crat 0crat added the scope label Feb 19, 2018
@0crat
Copy link
Collaborator

0crat commented Feb 19, 2018

Job #599 is now in scope, role is DEV

@0pdd
Copy link
Collaborator Author

0pdd commented Feb 23, 2018

@0pdd all puzzles are solved

@0pdd
Copy link
Collaborator Author

0pdd commented Mar 3, 2018

The puzzle 539-4e7a4000 has disappeared from the source code, that's why I closed this issue.

@0crat
Copy link
Collaborator

0crat commented Mar 3, 2018

The job #599 is now out of scope

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

No branches or pull requests

2 participants