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

Update children when a parent is updated #48

Open
gmkruger opened this issue May 19, 2022 · 3 comments
Open

Update children when a parent is updated #48

gmkruger opened this issue May 19, 2022 · 3 comments

Comments

@gmkruger
Copy link

Describe the bug
Extension don't respect the rule when need to close the childs

To Reproduce
Create a rule when close a parent then the children close too;
rule1
rule2

Expected behavior
When I close the parent it children closed too

What version are you on:
Extension Version:1.2.4 | Module Version:1.2.0

Additional context

@gmkruger gmkruger added @status/needs-triage @type/bug Something isn't working labels May 19, 2022
@joachimdalen
Copy link
Owner

joachimdalen commented May 20, 2022

Hi!

If I understand you correctly, the issue is that when you close a parent, you want the children to be close too?

This is currently not a feature as the extension only works upward in the hierarchy, and not downwards. If you closed a Task, then the extension would be able to close the parent elements that was User Story and Feature. However, closing a User Story will not close the Tasks underneath it.

I am currently working on some changes in the rule engine due to #44 , so I can see if this is possible to integrate.

@gmkruger
Copy link
Author

gmkruger commented Jun 10, 2022

Hi @joachimdalen, did you see if this is possible to integrate?

Thank you for the answers!

@joachimdalen joachimdalen added this to the 2.X.X milestone Jun 11, 2022
@joachimdalen joachimdalen changed the title Don't change childs Update children when a parent is updated Jun 11, 2022
@joachimdalen
Copy link
Owner

Hi there, sorry for the late reply!

I looked into this and will add it to the backlog. The entire extension is written with the concept of working from the child to the parent, not the other way. Implementing the wanted changes will require pretty large rewrites as both the rule engine and admin interface will need major rewrites. It will also introduce some complexity related to parent processing, children lookup and recursion.

Adding this to the V2 milestone, but that does not currently have any timeline. If I can figure out a way to solve this without a rewrite, I will move the timeline closer.

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

No branches or pull requests

2 participants