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

Valuator: error when trying to answer a suggestion assigned to me and other 🪲 #113

Open
martanducas opened this issue Dec 7, 2023 · 0 comments

Comments

@martanducas
Copy link

Describe the bug
As a valuator, when a suggestion is assigned to me, if there are multiple participatory documents in the participatory space, I have found multiple issues:

  • In can see all the participatory documents, and all the suggestion assigned to me in all of them. I don't know to which participatory document each suggestion belongs.
  • If a participatory document has not uploaded the PDF document, I get a server error (Participatory Document 1 in the video).
  • If I try to answer a suggestion that has been assigned to me, I get an error.
  • If I click to "Assemblies", I don't know how to go back to my assigned suggestions.

To Reproduce

  1. Create and publish multiple participatory documents in a participatory space
  2. Create a suggestion and assign a valuator
  3. Login as a valuator and try to answer the suggestion

Expected behavior
I expect:

  • Viewing only the participatory documents where I have suggestions assigned. Each participatory document should only display its suggestions.
  • As a valuator, I have to be able to answer a suggestion.
  • If I go to Assemblies/Processes, I should view the Assembly/Process where the participatory document belongs.

Screenshots
https://github.com/openpoke/decidim-module-participatory-documents/assets/72607737/45073893-d839-460c-a5a0-8f1c41d40f22

Extra data
URL: https://workshops.pokecode.net/assemblies/test-gpc

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

No branches or pull requests

1 participant