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

Feature: Plannings - allow to delete a planning #3239

Open
judramos opened this issue Oct 10, 2024 · 1 comment
Open

Feature: Plannings - allow to delete a planning #3239

judramos opened this issue Oct 10, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request refinement
Milestone

Comments

@judramos
Copy link

judramos commented Oct 10, 2024

Is your feature request related to a problem? Please describe.
Actually, it is not possible to delete a planning.

Describe the solution you'd like
Add a deletion button in the planning view (as for devices).

Describe alternatives you've considered
N/A

Additional context
N/A

@judramos judramos added enhancement New feature or request refinement labels Oct 10, 2024
@github-project-automation github-project-automation bot moved this to 🔦 Triage in IoT Hub Portal Oct 10, 2024
@judramos judramos added this to the v6.0 milestone Oct 10, 2024
@judramos judramos self-assigned this Oct 14, 2024
@judramos judramos moved this from 🔦 Triage to 📝 Todo in IoT Hub Portal Oct 14, 2024
@judramos
Copy link
Author

judramos commented Oct 17, 2024

  • The schedule must be deleted too (no delete cascade)
  • The planning in the layer must be deleted when the planning is deleted
  • The list of layers in the planning's screen should indicate if it's already linked to another planning

@judramos judramos moved this from 🚧 In Progress to 💬 Ready for Review in IoT Hub Portal Oct 31, 2024
@judramos judramos linked a pull request Nov 29, 2024 that will close this issue
9 tasks
kbeaugrand added a commit that referenced this issue Dec 5, 2024
* Add of layerId in device twin

* #2998 Quartz migration for SendPlanningCommand

* #2856 Disable built-in device model deletion

* #3238 Update view when a device is unchecked

* 3239 Allow to delete a planning from client

* 3239 Allow to delete a planning

* 2998 Schedule commands

* #3239 Change checkboxes for layers displayed

* Merge from main

* 2516 add supportLoRaFeatures tag in template file

* #3250 Import device list using the template given

* #2985 Batch import creates ABP tags in Device Twin for OTAA-based device models

* #3251 Import device - data overwritten

* Unit tests

* Update src/IoTHub.Portal.Infrastructure/Jobs/SendPlanningCommandJob.cs

Co-authored-by: Kevin BEAUGRAND <[email protected]>

* #2958 Remove 'Connection State' and 'Last status update' columns

* #3023 startupOrder not supported in Edge Device Model schema

---------

Co-authored-by: E068097 <[email protected]>
Co-authored-by: judramos <[email protected]>
kbeaugrand added a commit that referenced this issue Dec 5, 2024
* Add of layerId in device twin

* #2998 Quartz migration for SendPlanningCommand

* #2856 Disable built-in device model deletion

* #3238 Update view when a device is unchecked

* 3239 Allow to delete a planning from client

* 3239 Allow to delete a planning

* 2998 Schedule commands

* #3239 Change checkboxes for layers displayed

* Merge from main

* 2516 add supportLoRaFeatures tag in template file

* #3250 Import device list using the template given

* #2985 Batch import creates ABP tags in Device Twin for OTAA-based device models

* #3251 Import device - data overwritten

* Unit tests

* Update src/IoTHub.Portal.Infrastructure/Jobs/SendPlanningCommandJob.cs

Co-authored-by: Kevin BEAUGRAND <[email protected]>

* #2958 Remove 'Connection State' and 'Last status update' columns

* #3023 startupOrder not supported in Edge Device Model schema

---------

Co-authored-by: E068097 <[email protected]>
Co-authored-by: judramos <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refinement
Projects
Status: 💬 Ready for Review
Development

Successfully merging a pull request may close this issue.

1 participant