lose nesting using pre-existing data projects when update API #1652

New Issue

massimiliano-dalcero · 2023-11-22T10:50:05Z

2023-11-22 10:50:05 +00:00

Description

Hello,
when I use the new api (v0.21.0+213-bbc8da1e80), the olds sub-projedcts lose nesting (multi level).
Someone remains nested, but in general the hierarchy is lost

This issue happens both using the old version of the frontend (0.21.0+298-5f2787e18d) and the new one (0.21.0+368-282ec3164b).

When I restore the old API (v0.21.0+178-aad6bc08f6), everything goes back to normal.

I can't replicate the problem on vikunja demo site, because the problem occurs using pre-existing data.

Now my configuration is as follows and everything works correctly. But when I update the API, the nested project hierarchies are lost

Vikunja Frontend Version

v0.21.0+213-bbc8da1e80

Vikunja API Version

v0.21.0+213-bbc8da1e80

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

### Description Hello, when I use the new api (v0.21.0+213-bbc8da1e80), the olds sub-projedcts lose nesting (multi level). Someone remains nested, but in general the hierarchy is lost This issue happens both using the old version of the frontend (0.21.0+298-5f2787e18d) and the new one (0.21.0+368-282ec3164b). When I restore the old API (v0.21.0+178-aad6bc08f6), everything goes back to normal. I can't replicate the problem on vikunja demo site, because the problem occurs using pre-existing data. Now my configuration is as follows and everything works correctly. But when I update the API, the nested project hierarchies are lost ![image](/attachments/402b5996-157c-4955-b9ef-ea9efc5524aa) ### Vikunja Frontend Version v0.21.0+213-bbc8da1e80 ### Vikunja API Version v0.21.0+213-bbc8da1e80 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_

image.png

16 KiB

massimiliano-dalcero added the

kind/bug

label 2023-11-22 10:50:05 +00:00

massimiliano-dalcero changed title from ~~lose nesting using pre-existing data projects~~ to lose nesting using pre-existing data projects when update API

2023-11-22 11:13:09 +00:00

konrad commented

2023-11-22 14:45:46 +00:00

Is only the hierarchy lost? Or the projects themselves?

If you update and the hierarchy is lost, are you able to create new sub projects?

Can you provide exact steps to reproduce?

Is only the hierarchy lost? Or the projects themselves? If you update and the hierarchy is lost, are you able to create new sub projects? Can you provide exact steps to reproduce?

massimiliano-dalcero commented

2023-11-22 17:46:40 +00:00

I can't imagine a way to replicate the problem. It happens to me only by updating the API service binary (from v0.21.0+178-aad6bc08f6 to v0.21.0+213-bbc8da1e80).
After update, if I create a sub-project it is correctly under its parent, but the "old ones" remain excluded from their parents. I can't even move them manually.
After restore old api binary, all return okay. Also the new subproject created with "last api binary"-

The strange thing is that only a "10%" is nested, and everything else is flat, while maintaining the reference to its parent in the infos.

if I look in the sub-project info I see that it is nested in its parent. But graphically in the left bar everything remains flat.

in general, I didn't do anything strange. I only used version v0.21.0+178-aad6bc08f6 and updated to version v0.21.0+213-bbc8da1e80. We use and we have enabled infinite nesting under HTML in frontend.

Note that when using new frontend with old api binary, works all fine.

that's all :)
Sorry if I can't give more clues

I can't imagine a way to replicate the problem. It happens to me only by updating the API service binary (from v0.21.0+178-aad6bc08f6 to v0.21.0+213-bbc8da1e80). After update, if I create a sub-project it is correctly under its parent, but the "old ones" remain excluded from their parents. I can't even move them manually. After restore old api binary, all return okay. Also the new subproject created with "last api binary"- The strange thing is that only a "10%" is nested, and everything else is flat, while maintaining the reference to its parent in the infos. if I look in the sub-project info I see that it is nested in its parent. But graphically in the left bar everything remains flat. in general, I didn't do anything strange. I only used version v0.21.0+178-aad6bc08f6 and updated to version v0.21.0+213-bbc8da1e80. We use and we have enabled infinite nesting under HTML in frontend. Note that when using new frontend with old api binary, works all fine. that's all :) Sorry if I can't give more clues

konrad commented

2023-11-24 10:20:52 +00:00

but the "old ones" remain excluded from their parents. I can't even move them manually.

So you see them in the sidebar, but they are not associated to their parents?

Can you give an example of the structure before and after the upgrade?

> but the "old ones" remain excluded from their parents. I can't even move them manually. So you see them in the sidebar, but they are not associated to their parents? Can you give an example of the structure before and after the upgrade?

massimiliano-dalcero commented

2023-11-24 10:45:46 +00:00

Hi @konrad ,
can I send privately?

There are customer names in the tree and I would prefer not to write them publicly.

If you want, I can also privately send you the sqlite db for testing purposes.

Hi @konrad , can I send privately? There are customer names in the tree and I would prefer not to write them publicly. If you want, I can also privately send you the sqlite db for testing purposes.

konrad commented

2023-11-24 12:56:50 +00:00

Sure, you can send it to me via konrad@vikunja.io - but you can also obfuscate the names and post here.

massimiliano-dalcero commented

2023-11-27 14:32:54 +00:00

Hello @konrad ,
thanks for your support, I am aware that this is an unusual problem, but I hope it can be useful.
I sent you the material privately. If you have not received it, please do not hesitate to inform me :)

Best regards,
Massimiliano

Hello @konrad , thanks for your support, I am aware that this is an unusual problem, but I hope it can be useful. I sent you the material privately. If you have not received it, please do not hesitate to inform me :) Best regards, Massimiliano

👍 1

massimiliano-dalcero commented

2024-02-01 10:36:05 +00:00

All fixed with 0.22 version :)

massimiliano-dalcero closed this issue

2024-02-01 10:36:05 +00:00

konrad referenced this issue from a commit

2024-02-07 14:00:32 +00:00

chore(deps): update typescript-eslint monorepo to v5.14.0 (#1652)

Sign in to join this conversation.