Make the ,,CNP'' field OPTIONAL in the volunteer profile/add volunteer form.

Within issue #135 , we implemented a new checkbox in the document's form (see issue #135 for more details)
The problem is that the checkbox only appears in the document's form/details page if accessed through the following path: Documente/ Document individual.
If the same document is accessed through the following path: Organizații/Porifl organizație/Documente tab/ Document individual
the checkbox doesn't exist.

Implement the checkbox in the individual document's form/details page, regardless of the access path.

Go to 'Organisations' from side navigation > Click on 'Create organisation' button > Populate the 'Denumirea organizatiei' field with a value > when you populate the field, it is autofilling the 'Alias organizație' field with the same value

Expected behavior: the filed 'Alias organizație' should not be mandatory; if the user does not populate the field with any value, it will be autopopulated with the value from the 'Denumirea organizatiei' field but only after saving the entity

Go to 'Organisations' from side navigation > Click on a table row > Notice that the page title is 'Editare Organisation'
The page title should be the name of the organisation (value from filed ''Denumire organizație'')

Update roles and permissions according to this document.

The side navigation bar consists of 6 buttons: 'Panoul de control', 'Documents', Organisations', 'Resources', 'Users', 'Volunteers';
The architecture of each button consists of an icon and the label.
Currently, the used icons don't suit the label. To be discussed, depending on the available icons library, which icons are best for each button.

Describe the bug
When you add a new document and try to save it, an error is displayed. After you close the error and click on 'Anulare,' it takes you back to the documents list, and you can notice that the document you tried to save and failed was indeed saved in DB.

To reproduce

1. Go to the 'Documente' section
2. Click on the 'Adăugare Document' button
3. Fill in all the field
4. Click on 'Salvare'
5. Notice the error displayed
6. Close the error message
7. Click on 'Anulare'
8. Notice that the document has been saved in db, and it is displayed in the table

Expected bahavior
When the user clicks on the 'Salvare' button the entry should be saved in db and the user must be shown the newly created entry in view mode.

There should be no 'Interventions' section in the organization profile at this state of the project.
You can notice the 'Interventions' in the tab component if you go to the organization profile.

Remove the section from MVP.a

Go to Organisations from the side navigation > Click on 'Județ' field from the filters section > Try pick two counties that you want to filter the db based on > You fail because the field is single select
Repeat the same process for 'Tipul organizației' filed > Same result

Expected behavior: the fields should allow multiple choices

Go to 'Organisations' from side navigation > Click on a table row > Notice that the first tab is named 'Editare'
Change tab name to 'Profil'

1. Add document

Implement fields from ''Add document'' sheet from the data dictionary in:
Go to 'Document' from side navigation > Click on 'Adăugare document' button > implement fields in 'Creare document' form

2. Add Organisation

Implement fields from ''Add Organisation'' sheet from the data dictionary in:
Go to 'Organisations' from side navigation > Click on 'Create organisation' button > implement fields in 'Adaugă organizație nouă' form

3. Organisation Profile - General data

Implement fields from ''Organisation Profile - General data'' sheet from the data dictionary in:
Go to 'Organisations' from side navigation > Click on an individual organisation from the table > implement fields in 'Date generale' tab

4. Organisation Profile - Activity

Implement fields from ''Organisation Profile - Activity'' sheet from the data dictionary in:
Go to 'Organisations' from side navigation > Click on an individual organisation from the table > implement fields in 'Activitate' tab

5. Add Resource

Implement fields from ''Add Resource'' sheet from the data dictionary in:
Go to 'Resources' from side navigation > Click on 'Adăugare resource' button > implement fields in 'Creare Resource' form

6. Add User

Implement fields from ''Add User'' sheet from the data dictionary in:
Go to 'Users' from side navigation > Click on 'Adăugare user' button > implement fields in 'Creare User' form

7. Add Volunteer

Implement fields from ''Add Volunteer'' sheet from the data dictionary in:
Go to 'Volunteers' from side navigation > Click on 'Adăugare volunteer' button > implement fields in 'Creare Volunteer' form

Admin DSU user should be able to filter the organisations by 'Arie de activitate' (Local; Regional; Național; Internațional;) + by county/region depending on the value selected (more details after solving issue #117 )

To clarify how we want to segment the organizations by area of activity.

Change the label from 'Users' to 'Utilizatori' in the organisation's profile (tab component).

Implement 'Profil organizație' page for Admin Organizație user type. The Admin ONG should be able to view and update the organization's profile. Implement the page as depicted in figma/image below:

This endpoint should be accessible at /api/resources and include the following fields:

• ID
• Denumire resursă
• Județ
• Organizație:
  • ID
  • Nume
• Categorie:
  • ID
  • Nume
• Subcategorie:
  • ID
  • Nume
• Tip:
  • ID
  • Nume
• Created at
• Updated at

Organization ID 10 can't define any values for Aria de activitate. This error is displayed when any values is selected for the field Organizația își desfășoară activitatea pe plan

1. After 11 months from signed_at send reminder to NGO and Admin DSU that the protocol will expire.

Email text:
"Bună,

protocolul dintre [nume_organizatie] și Departamentul pentru Situații de Urgență va expira în 30 de zile.
Dacă aceste nu este prelungit, veți pierde accesul în aplicație de management de resurse.

Mulțumim,
Echipa DSU"

2. After 12 months from [signed_at] send notification to NGO and Admin DSU that the protocol has expired.

Email text:
"Bună,

protocolul dintre [nume_organizatie] și Departamentul pentru Situații de Urgență a expirat.

Mulțumim,
Echipa DSU"

Go to 'Documents' from side navigation > Click on 'Adăugare document' button > Populate the 'Signed at' field with a value > Populate the 'Expire at' with a value > Click on 'Protocol' field > Upload a document > Click on 'Creare' button
There was displayed the following error:

Across platform, the language should be consistent. In this case, all texts should be in Romanian.

When I upload a file I want to see the file name in the documents table instead of a simple placeholder.

Change the page title from 'Vizualizare Resursă' to 'valure from 'Denumire resursă' field

Implement import excel with volunteers. TBD excel template and other details

Describe the bug
When you edit an entity in the platform (resource, organization, etc.), after making the change, the page remains in edit mode when you click 'Salvare'.

To Reproduce

1. Go to the 'Resurse' section
2. Click on an individual resource
3. Click on the 'Editare' button
4. Click on the 'Salvare' button
5. Notice that the success message is displayed, but the page remains in edit mode

Expected behavior
When you click on the 'Salvare' button, the changes should be saved and the page should go back to view mode.

The README instructs the user to run:

docker run --rm -it code4romania/rvm php artisan key:generate --show

as part of the initial setup. If that command doesn't find a local image named code4romania/rvm, it tries to pull from Docker Hub code4romania/rvm:latest. But on Docker Hub, there is no image with that tag, only one with the edge tag.

Change the field label from 'Parola' to 'Confirmă parola'

Describe the bug
Coordonator IGSU/ISUJ should NOT be able to Activate/Deactivate organizations. Currently, the ,,Activeazză''/,,Dezactivează'' is displayed in organization's profile for this user type.

To Reproduce
Steps to reproduce the behavior:

1. Log in as Coordonator IGSU/ISUJ
2. Go to Organizații page
3. View an individual organization
4. See the Activează/Dezactivează button in the top right corner of the page

Expected behavior
REMOVE the Activează/Dezactivează button for the Coordonator IGSU/ISUJ user type.

Update Field_Values for ''Tipul organizație'': ONG; Entitate privată; Instituție publică; Mediu academic;

IF Field_Value 'ONG' selected, display ''Tipul ONG-ului' field having the following Field_Values: Asociație; Fundație; Federație; (single select, mandatory)

Change the page title from 'Acceptă invitația' to 'Setează parola'

Go to 'Organisations' from side navigation > Click on 'Create organisation' button > Populate the fields > Click on 'Confirmare'
After clicking on 'Confirmare' there is no invitation sent to the email address.

Expected behavior: after adding an organisation in the platform, an email should be sent to the email address from the 'Email de contact organizatie' filed; The email should contain:

• a message to let the user know that it has been added to the platform
• instructions regarding the log in credentials
• a reset password link
  To be discussed about details with the UX

Go to 'Organisations' from side navigation > Click on 'Create organisation' button > Populate the fields > Click on 'Confirmare'
After clicking on 'Confirmare' the side panel collapses and there is no success message displayed.

Expected behavior: after adding an organisation, there should be displayed a success message (similar to the following one):

Implement the following checkbox under the 'Dată expirare' field: 'Încheiat pe perioadă nedeterminată'
If checked => the protocol will NOT have an expiring date (so the 'Dată expirare field becomes disabled), and it will not be taken in consideration when the system checks the db for reminders

Implement fields from ''Add Resource'' sheet from the data dictionary in:
Go to 'Resources' from side navigation > Click on 'Adăugare resource' button > implement fields in 'Creare Resource' form

Continues #70 and #73

Replace the existing logo with this one

Describe the bug
If the user wants to filter the resource database by a certain category, it will display all values in subcategorie and tip fields, not only the corresponding values to that certain category the user wants to filter the database by.

Expected behavior
When you filter by a specific category, for subcategorie and tip fields/filters, it should display only the corresponding values to that category, as the data dictionary explains. (see Add Resource sheet)

Describe the bug
When you add a new volunteer and you fill in the required fields, it displays an error when you want to search for a 'Localitate'

To Reproduce

1. Go to 'Voluntari' section
2. Click on 'Adăugare voluntar' button
3. Try fill in the 'Localitate' field
4. Notice the error

When you click on a dropdown filed, it displays the list and the field changes to a focus state. When you click on the filed it triggers the collapse of the list but it remains in the focus state.
In order to see the behavior follow the next steps:
Log in > Click on 'Organisations' from side navigation bar > Click on 'Județ' OR 'Tipul organizației' fields from the filters section > Click again on the field

Expected behavior: When a user clicks on the field, the list should be displayed and the filed should be in focus state; when the user clicks again on the field or outside the field, the list should be collapsed and the field should get back to default state.

The README links to a docker-compose.yml file that is no longer in the repo.

Go to 'Documents' from side navigation > Click on a table row to open an entity
The user can't view or download the file attached to that entity.
It is critical for the user to view AND download the file that is attached to the entity.

The current primary color is #F7B13C (with the corresponding gradient illustrated below). Change the primary color from #F7B13C to #264998. Replace the primary color with the new one.

Current color gradient:

EXPECTED COLOR GRADIENT:

This endpoint should be accessible at /api/organisations and include the following fields::

• ID
• Denumire organizație
• Tip organizație
• Status
• Sediu
• Aria de expertiză:
  • ID
  • Nume
• Categorie de risc:
  • ID
  • Nume
• Tipuri de acțiuni
• Aria de activitate
• Județ
• Created at
• Updated at
• Volunteers count

DSU requested an API on RVM to automatically import the data from the dashboard (e.g. number of active protocols) to the DSU website.

Create endpoints for:

• #150
• #151

Other relevant issues:

• API access should be authenticated
• Responses should not be paginated
• #153

When you add a user to the platform, the email should have the following structure and content:

Ești invitat să te alături platformei RVM - Sistemul de management de resurse umane și materiale în cazul unui dezastru, administrat de Departamentul Situații de Urgență al României.
Acceptă invitația (link attached to this phrase) pentru a-ți putea accesa contul.
Link to the password setting page / Acceptă invitația button that will take user to password setting page

Go to RVM sign in as DSU Admin > Volunteers from side menu > notice the 'Acreditare prim ajutor' column
Currently, the data field 'Acreditare prim ajutor' is displayed in the table using toggle component
It needs to be displayed as plain text ''Yes'' / ''No''; the value should be editable only in Volunteer edit mode NOT directly from table view

In the Panoul de control section should be displayed the following statistics, using the components shown below in screenshot:

1. Total number of organisations in db
2. Total number of resources in db
3. Total number of volunteers in db
   

The user should be able do export a table in a .CSV .XLX format

When an organization is added to the platform, the only information filled in is
Denumire organizație; Alias organizație; Email; Telefon; Tip organizație.
The Admin ONG user must add all the other information about the organization in ,,Profil organizație'' section.
Since most of the fields in ,,Profil organizație'' are MANDATORY, when the user wants to edit a piece of information about the organization, they have to fill in all the mandatory fields to be able to save the entry.
This constrain could create frustration because the user must fill in all mandatory information at once, otherwise, they won't be able to save the changes.
To explore if we make all the fields in ,,Profil organizație' optional or not.