You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
As an admin, I cannot change the type of an initiative sent in technical validation. Indeed, when I update the initiative after changing its type, the new type is not taking in account and the previous remains.
To Reproduce
Go to /admin/initiatives
Click on the initiative configuration button of an initiative sent in technical validation
Modify the "Type" field (at least 2 initiatives types must be created)
Update the changes
See that the new initiative type is not applied
Expected behavior
As an admin, I should be able to change the type of an initiative sent in technical validation.
Screenshots Original type of the initiative Changing the type and updating it Changing the type and updating it
Additional context
Unable to reproduce on nightly.decidim.org (0.28v) !
The text was updated successfully, but these errors were encountered:
The impossibility of changing the type of an initiative seems to be linked to sectors: I can change the type of an initiative as long as the sector remains unchanged. In concrete terms, this means that I can change the type A of an initiative to type B if the sector of type A is the same for type B. If the sector of type A is different from the sector selected for type B, I cannot change the sector.
Describe the bug
As an admin, I cannot change the type of an initiative sent in technical validation. Indeed, when I update the initiative after changing its type, the new type is not taking in account and the previous remains.
To Reproduce
Expected behavior
As an admin, I should be able to change the type of an initiative sent in technical validation.
Screenshots
Original type of the initiative
Changing the type and updating it
Changing the type and updating it
Additional context
Unable to reproduce on nightly.decidim.org (0.28v) !
The text was updated successfully, but these errors were encountered: