-
Notifications
You must be signed in to change notification settings - Fork 93
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
[New Epic Feature] Create a new campaign request from website #1842
Labels
type: enhancement
New feature or request
Comments
1 task
sashko9807
pushed a commit
that referenced
this issue
Jun 18, 2024
gparlakov
pushed a commit
to gparlakov/podkrepi-bg-frontend
that referenced
this issue
Jun 19, 2024
…pi-bg#1842) (podkrepi-bg#1855) * create a protected route for campaign applications * fix: self-closing tag linter error
sashko9807
pushed a commit
that referenced
this issue
Jun 21, 2024
) * create a protected route for campaign applications * feat: create campaign-application steps components * feat: create campaign-application stepper component * feat: create stepper icon component * feat: render the stepper in the campaign application page * fix: adjust Stepper styles according to Figma design * feat: add actions buttons for the stepper * feat: add translations for the stepper action buttons * fix: adjust action buttons styles and functionality * lint: remove empty type
This was referenced Jun 22, 2024
sashko9807
pushed a commit
that referenced
this issue
Jun 26, 2024
* feat: add remark in the stepper * add translations for step one * refactor action buttons styles * create CampaignApplicationOrganizer component * edit CampaignApplicationOrganizer * add yup validation to campaign application organizer form * fix styles to be responsive * fix: adjust spacing between fields and buttons to be the same * refactor organizer step form according to endpoint schema * refactor action buttons styles
gparlakov
added a commit
to gparlakov/podkrepi-bg-frontend
that referenced
this issue
Jun 30, 2024
- issue podkrepi-bg#1842 - add a admin space for the campaign applications - only skeleton - will be fleshed out iteratively - add admin edit campaign application - it will show all the steps of the stepper (create campaign application) with addition of the admin-only editable stuff
1 task
sashko9807
pushed a commit
that referenced
this issue
Jul 1, 2024
…#1866) * feat: add remark in the stepper * add translations for step one * refactor action buttons styles * create CampaignApplicationOrganizer component * edit CampaignApplicationOrganizer * add yup validation to campaign application organizer form * fix styles to be responsive * fix: adjust spacing between fields and buttons to be the same * refactor organizer step form according to endpoint schema * refactor action buttons styles * add checkboxes for accepting general terms and gdpr * rename checkbox values correctly * remove not used import
This was referenced Jul 1, 2024
Merged
sashko9807
pushed a commit
that referenced
this issue
Jul 5, 2024
* feat: campaign application admin init - issue #1842 - add a admin space for the campaign applications - only skeleton - will be fleshed out iteratively - add admin edit campaign application - it will show all the steps of the stepper (create campaign application) with addition of the admin-only editable stuff * Update EditPage.tsx * fix: linting for campaign application admin edit
sashko9807
pushed a commit
that referenced
this issue
Jul 17, 2024
gparlakov
added a commit
to gparlakov/podkrepi-bg-frontend
that referenced
this issue
Jul 29, 2024
podkrepi-bg#1842 - add missing field title and relationship - send post
sashko9807
pushed a commit
that referenced
this issue
Aug 26, 2024
* feat: create application #1842 - add missing field title and relationship - send post * fix: add beneficiary relationship
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which area(s) of Podkrepi.bg are affected? (leave empty if unsure)
Campaigns
Describe the feature you'd like to request
First things first: In order to better understand this feature, you will need to know the main stakeholders and terms. You can find information here . The text is in Bulgarian, you can user Google translate if you need help with the translation
Current workflow: If somebody wants to start a campaign on podkrepi.bg website, he or she starts by filling in a Google form. The form can be found here.
The form is assigned to a member of campaigns "department" and the volunteer initiates all the necessary steps to ensure that the form is correctly filled out, there is enough information about the campaign, finances, gathers expert opinion (if needed). This is done by updating the information in a Google Sheet - a template can be found here, adding documentes to Google Drive and exchanging emails, phone calls and/ or meeting with the organizer of the campaign or experts on the campaign subject. Tasks are tracked via Trello Board.
After all the information has been gathered and checked (which can take multiple iterations with the Organizers), three members of the Podkrepi.bg Board should approve the start of the campaign.
Our task: Our task here is to enable Organizers to create a new Campaign Request from podkrepi.bg website and be able to edit the Request following off-system communication with podkrepi.bg volunteers. We will need to create a MVP of the process (basic features only). In time with additional feature requests we will expand this feature to include additional user stories. The main task, though, is to have a working Campaign Request form in the platform and Campaigns team to be able to oversee the Campaign approval process through the platform's admin panel.
Describe the solution you'd like
Design: Campaign Request creation prototype can be found here
In admin panel users with the necessary rights should have a list view, edit form, add form of a Campaign Request.
User Stories: User stories (in Bulgarian) can be found here
Можеш ли да edit-неш линка в issue-то, моля). The list includes MVP and Later user stories and is negotiable :)
Describe alternatives you've considered
No response
The text was updated successfully, but these errors were encountered: