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

R11. Store at least one individual resopnse template #27

Closed
2 tasks done
paarals opened this issue Sep 14, 2022 · 2 comments
Closed
2 tasks done

R11. Store at least one individual resopnse template #27

paarals opened this issue Sep 14, 2022 · 2 comments

Comments

@paarals
Copy link
Contributor

paarals commented Sep 14, 2022

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

Describe the solution you'd like
As a process-admin, I would like to be able to store at least one individual response template for each process, built into the response field or below (e.g. customizable with Term Customizer).

Mock up

Does this issue could impact on users private data?

Acceptance criteria

  • As a super-admin, I can store answers proposals as a template

Technical specifications
See openpoke/decidim#34

Implementation

Testing

  1. As a super-admin, go to templates: https://letterbox.dev.pokecode.net/admin/templates/proposal_answer_templates
  2. Go to a Proposal Answer section
  3. Create a new Proposal Answer
  4. Save new proposal answer with its scope
  5. As an admin-process, valuator, go to participatory process: https://letterbox.dev.pokecode.net/admin/participatory_processes/digital-letterbox/components/2/manage/proposals/14
  6. Go to Damage Report component
  7. Answer one Damage Proposal
  8. Select template available for scope
  9. Send the answer!

Additional context

@microstudi microstudi moved this from Peparation to Product Backlog in Digital Letterbox / Damage Reporting Sep 29, 2022
@paarals paarals moved this from Product Backlog to Sprint Backlog in Digital Letterbox / Damage Reporting Oct 11, 2022
@paarals paarals moved this from Sprint Backlog to Product Backlog in Digital Letterbox / Damage Reporting Oct 11, 2022
@paarals paarals moved this from Product Backlog to Sprint Backlog in Digital Letterbox / Damage Reporting Oct 11, 2022
@microstudi microstudi moved this from Sprint Backlog to Doing in Digital Letterbox / Damage Reporting Oct 11, 2022
@paarals paarals moved this from Ready to QA Testing in Digital Letterbox / Damage Reporting Oct 18, 2022
@paarals
Copy link
Contributor Author

paarals commented Nov 4, 2022

@paarals paarals moved this from QA Testing to Corrections in Digital Letterbox / Damage Reporting Nov 7, 2022
@paarals
Copy link
Contributor Author

paarals commented Jan 23, 2023

closed by openpoke/decidim#41

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

No branches or pull requests

1 participant