Now that voting is in the pipeline, we would like to automate the way that votings are created for budget approval by the council. == Creation == Voting creation should be triggered by this condition: A bug under "Mozilla Reps":"Budget Requests" gets a need-info flag "?" "email@example.com" Fields for voting creation: Voting Name: Bug Summary Description: Bug Comment 0 (description) + bugzilla url Start Date and Time: Trigger time End Date and Time: Start date and time + 72 hours Eligible Group: council One radio poll with: Title: Budget Approval Answer 1: Approved Answer 2: Denied == Email notifications == Overriding the standard notification policy we would like to have the following. If a voting is created based on the afore mentioned condition then the emails (about creation, reminder, results etc) should be sent to reps-council ^at mozilla ^dot com and not to the individual council members. This should not affect votings created with "council" group as eligible voters in general. == Period extension == In case that less than 50% of the council has casted votes, voting should be extended for 24h and email reminders should continue as usual. == Commenting *optional* == Explore the *option* to have comments within this type of voting. (if not, the comments can be posted through the emails, as this was the reasoning for changing the recipient of the email notifications.) If it is possible then we might need restructuring of views to facilitate viewing of a vote after you casted a vote.
Assignee: nobody → tasos
Status: NEW → ASSIGNED
I'm a bit curious about the implementation planning. Are we going to poll all the bugs with: Summary "Budget Request" in Component "Budget Requests" of Product "Mozilla Reps" on regular interval to check for a new needinfo flag, after the last polling?
We can ask bugzilla's API to return all bugs in a Component which have been updated since a timestamp. So we will not request all bugs in a component but only the bugs that have been updated. Then we extract information from each bug and check if the needinfo flag was set. Does this answer your question?
(In reply to Giorgos Logiotatidis [:giorgos] from comment #2) > We can ask bugzilla's API to return all bugs in a Component which have been > updated since a timestamp. Still needs polling, but much efficient/precise. Thumbs up! > Does this answer your question? Yep, thanks :)
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Reopening this bug. Some small changes were suggested by Council before they start using this awesome new feature. I will link those to this bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
All great tracking bugs must come to an end. Now that all the blocking bugs are resolved, I am delighted to close this one as well. Thanks for all the hard work! Budget requests will now be faster than fast. Hooray!
Status: REOPENED → RESOLVED
Closed: 6 years ago → 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.