Initiatives thresholds configuration

Pauline Bessoles 25/05/2020 13:44 Withdrawn

Is your feature request related to a problem? Please describe.

Initiatives can be accepted or rejected at the end of signature collection period when they succeeded or failed to reach the support required threshold. It would be interesting to be able to implement different behaviors for milestones leading up to that that signature threshold (like for PP steps).

Three milestones already exist per default : 25%, 50% and 75% of the signatures required. When reached, a notification is sent. These are configured directly in the code and do not a have corresponding UI in the admin so that we have flexibility to configure it.

Describe the solution you'd like

As an admin, I want to be able to configure different milestones when configuring an initiative type scope.

As an admin I want to have a config flag that will make the jauge to be responsive to the milestones.

Ex : if milestones are configured as : Milestone 1 = 20% (10K signatures) and Milestone 2 = 100% (50K signatures). Then at first I want the jauge to display 10k when passed it can display the next milestone 50k.

Back-Office

/admin/initiatives_types/1/edit

Configurable milestones

[ ] Add config flag that allows admin to config milestone percentage
[ ] when clicked default milestones in editable fields that way the admin can set its own percentage
[ ] allow admin to delete a milestone
[ ] add a button "Add milestone" to allow admin to add a milestone

[ ] When all milestones have been removed, the default milestones don't apply
[ ] When the custom milestones percentages are disabled, the default milestones apply

Adaptable jauges

[ ] Add a config flag so that the admin can choose if wants its jauge to be adaptable to milestones

Front-Office

/initiatives : Change the initiative card gauge when threshold is reached
SHOW : /initiatives/i-1 : Change the initiative show gauge when threshold is reached

Describe alternatives you've considered

None

Does this issue could impact on users private data?

No Funded by

Comment

Fingerprint

The piece of text below is a shortened, hashed representation of this content. It is useful to ensure the content has not been tampered with, as a single modification would result in a totally different value.

Value: 1d12745f7ad7b32a5f2a7555f373341bf2d4bcbcf4280cb4e1a5d228b2fafac4

Source:

{"body":{"en":"<h2><strong>Is your feature request related to a problem? Please describe.</strong></h2><p>Initiatives can be accepted or rejected at the end of signature collection period when they succeeded or failed to reach the support required threshold. It would be interesting to be able to implement different behaviors for milestones leading up to that that signature threshold (like for PP steps).</p><p>Three milestones already exist per default : 25%, 50% and 75% of the signatures required. When reached, a notification is sent. These are configured directly in the code and do not a have corresponding UI in the admin so that we have flexibility to configure it.</p><h2><strong>Describe the solution you'd like</strong></h2><p>As an admin, I want to be able to configure different milestones when configuring an initiative type scope.</p><p>As an admin I want to have a config flag that will make the jauge to be responsive to the milestones.</p><p>Ex : if milestones are configured as : Milestone 1 = 20% (10K signatures) and Milestone 2 = 100% (50K signatures). Then at first I want the jauge to display 10k when passed it can display the next milestone 50k.</p><h3>Back-Office</h3><ul><li>/admin/initiatives_types/1/edit</li></ul><h3><em>Configurable milestones</em></h3><ul><li>[ ] Add config flag that allows admin to config milestone percentage</li><li>[ ] when clicked default milestones in editable fields that way the admin can set its own percentage</li><li>[ ] allow admin to delete a milestone</li><li>[ ] add a button \"Add milestone\" to allow admin to add a milestone</li></ul><p><br></p><ul><li>[ ] When all milestones have been removed, the default milestones don't apply</li><li>[ ] When the custom milestones percentages are disabled, the default milestones apply</li></ul><h3><em>Adaptable jauges</em></h3><ul><li>[ ] Add a config flag so that the admin can choose if wants its jauge to be adaptable to milestones</li></ul><h3>Front-Office</h3><ul><li>/initiatives : <em>Change the initiative card gauge when threshold is reached</em></li><li>SHOW : /initiatives/i-1 : <em>Change the initiative show gauge when threshold is reached</em></li></ul><p>\r\n<strong>Describe alternatives you've considered</strong></p><p>None</p><p>\r\n</p><p>\r\n<strong>Does this issue could impact on users private data?</strong></p><p>\r\nNo\r\n\r\n<strong>Funded by</strong>\r\n</p><p>AN</p>"},"title":{"en":"Initiatives thresholds configuration"}}

This fingerprint is calculated using a SHA256 hashing algorithm. In order to replicate it yourself, you can use an MD5 calculator online and copy-paste the source data.

Comment details

Best rated

Recent

Older

Most discussed

You are seeing a single comment

View all comments

Pauline Bessoles 25/05/2020 15:26

Thanks for your questions @Armand-OSP ! When no milestones are set, the default milestones applies (25,50,75,100).
Milestones should be linked to an initiative type scope, a subdivision of initiative type

Essential

Preferences

Analytics and statistics

Marketing

Initiatives thresholds configuration

Is your feature request related to a problem? Please describe.