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

Agenda.java:37-42: Title element, of an order in agenda,... #843

Closed
0pdd opened this issue Mar 20, 2018 · 29 comments
Closed

Agenda.java:37-42: Title element, of an order in agenda,... #843

0pdd opened this issue Mar 20, 2018 · 29 comments

Comments

@0pdd
Copy link
Collaborator

0pdd commented Mar 20, 2018

The puzzle 422-1711e986 from #422 has to be resolved:

* @todo #422:30min Title element, of an order in agenda, has been declared in
* agenda.xsd. Let's add method title(...), which will set the title of
* on order and add a new stakeholder, set_agenda_title_from_github.groovy,
* which will get title of a job from GitHub and set it to Agenda. THe reason
* for the new stakeholder is that not all orders will come from Github, some
* may also come from Jira, Trello etc, in the future.

The puzzle was created by amihaiemil on 19-Mar-18.

Estimate: 30 minutes, role: DEV.

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 Mar 20, 2018

@yegor256/z please, pay attention to this issue

@0crat 0crat added the scope label Mar 20, 2018
@0crat
Copy link
Collaborator

0crat commented Mar 20, 2018

Job #843 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented May 19, 2018

The job #843 assigned to @proshin-roman/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this

@0crat
Copy link
Collaborator

0crat commented May 24, 2018

@proshin-roman/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

@proshin-roman
Copy link
Contributor

@0crat refuse

@proshin-roman
Copy link
Contributor

proshin-roman commented Jun 5, 2018

@0crat wait for PR #1095 to be reviewed and merged.

@0crat
Copy link
Collaborator

0crat commented Jun 5, 2018

@0crat refuse (here)

@proshin-roman The user @proshin-roman/z resigned from #843, please stop working. Reason for job resignation: Order was cancelled

@0crat
Copy link
Collaborator

0crat commented Jun 5, 2018

@0crat wait for #1095 (here)

@proshin-roman Job #843 is not assigned, can't put it on hold

@0crat
Copy link
Collaborator

0crat commented Jun 5, 2018

Tasks refusal is discouraged, see §6: -15 point(s) just awarded to @proshin-roman/z

@proshin-roman
Copy link
Contributor

@g4s8 Could you assign this ticket back to me, please? So that I can continue with the pull request (it needs a few adjustments). I've refused the ticket myself, but 0crat didn't react to it and then I continued working on this ticket by mistake. Now the pull request is already submitted, but 0crat refused the ticket.

@0crat
Copy link
Collaborator

0crat commented Jun 5, 2018

The job #843 assigned to @g4s8/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job

@g4s8
Copy link
Collaborator

g4s8 commented Jun 5, 2018

@0crat assign @proshin-roman

@0crat
Copy link
Collaborator

0crat commented Jun 5, 2018

@0crat assign @proshin-roman (here)

@g4s8 The job #843 assigned to @proshin-roman/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; we should be aware that @proshin-roman/z is on vacation; this ticket may be delayed; there will be a monetary reward for this job

@0crat
Copy link
Collaborator

0crat commented Jun 5, 2018

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @g4s8/z

@proshin-roman
Copy link
Contributor

@g4s8 thanks a lot! 👍

@0pdd
Copy link
Collaborator Author

0pdd commented Jun 6, 2018

The puzzle 422-1711e986 has disappeared from the source code, that's why I closed this issue.

@0pdd
Copy link
Collaborator Author

0pdd commented Jun 6, 2018

@0pdd the puzzle #1105 is still not solved.

@0crat
Copy link
Collaborator

0crat commented Jun 6, 2018

@ypshenychka/z please review this job completed by @proshin-roman/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@0crat 0crat removed the scope label Jun 6, 2018
@0crat
Copy link
Collaborator

0crat commented Jun 6, 2018

The job #843 is now out of scope

@ypshenychka
Copy link

@proshin-roman According to our QA Rules:

All impediments registered in the ticket have explanations of the reasons and links to related tickets, if necessary

Please add more details to the registered impediment.

@proshin-roman
Copy link
Contributor

proshin-roman commented Jun 7, 2018

@ypshenychka I had to set impediment just because I couldn't resolve the issue in 10 days. But anyway the impediment was not registered by 0crat.
UPD: sorry, I understood you wrong :) Doesn't the impediment have enough explanation in form of a link to a pull request?

@ypshenychka
Copy link

@proshin-roman Link is good, but there is no reason said what exactly are you waiting in PR. E.g. "wait for #1095 to be reviewed\merged etc." or any other valid reason.

@proshin-roman
Copy link
Contributor

proshin-roman commented Jun 7, 2018

@ypshenychka ok, I see you - going to fix the message then.
UPD: done.

@ypshenychka
Copy link

@proshin-roman Thank you!

@ypshenychka
Copy link

@0crat quality acceptable

@0crat
Copy link
Collaborator

0crat commented Jun 7, 2018

Order was finished, quality is "acceptable": +30 point(s) just awarded to @proshin-roman/z

@0crat
Copy link
Collaborator

0crat commented Jun 7, 2018

Quality review completed: +8 point(s) just awarded to @ypshenychka/z

@0pdd
Copy link
Collaborator Author

0pdd commented Jun 14, 2018

@0pdd the puzzle #1152 is still not solved; solved: #1105.

@0pdd
Copy link
Collaborator Author

0pdd commented Jul 2, 2018

@0pdd all 2 puzzles are solved here: #1105, #1152.

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

5 participants