-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Feature Request: Ability to Move all Child Items when the Location of the Parent Item is Changed #110
Comments
Bulk actions from #139 should be merged with this issue |
Solved by @slid1amo2n3e4 via pull request: #275 Errors
|
@kav2k Is there another way to receive the bounty? Like Paysend or Paypal? boss.dev does not support my country, and I have not received any response from them on my multiple emails. Obviously with any fees subtracted from the bounty, if need be. |
Hi @slid1amo2n3e4 - I promise to look into it early next week, but I am very busy this weekend. |
No worries, have a good one. |
I would say I have verified this to my satisfaction. @slid1amo2n3e4 I am open to directly using PayPal, but there's a question of securely communicating your email for that to me. |
Sent. Please confirm here and I will then withdraw the boss.dev bounty. |
Got it. Thank you very much. Are you okay doing it this way with other bounties too, if that were to happen? |
What is the problem you are trying to solve with this feature?
Currently, the location of a child item is not tied to the parent item. For example, if the location on a parent item is changed, the user must manually go into each child item & update the location manually to match. This can create a situation where, if the user doesn't double-check all the child items, the locations could vary and effect accurate location value roll-up.
What is the solution you are proposing?
A toggle tooltip/switch which a user can select at the parent item level, linking the location of the parent item to all child items beneath it. To maintain flexibility with other user set-ups/use cases, I think it's advisable to keep this as an 'opt in' feature, for users who may want to keep the 'location' of parent/child items decoupled.
What alternatives have you considered?
N/A, although I'm sure if I had a better understanding of the API, there could be a work around to this.
Additional context
No response
Contributions
The text was updated successfully, but these errors were encountered: