Skip to content

Clean up workflow and tasks when project is archived #1061

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

Closed
FyreByrd opened this issue Dec 12, 2024 · 2 comments · Fixed by #1111
Closed

Clean up workflow and tasks when project is archived #1061

FyreByrd opened this issue Dec 12, 2024 · 2 comments · Fixed by #1111
Labels
enhancement New feature or request svelte-rewrite Issue for the S2 upgrade to Svelte

Comments

@FyreByrd
Copy link

Currently, when archiving/reactivating a project, all it does is set/unset Project.DateArchived.

Suggested behavior for discussion:
On Archival:

  • Clean up all user tasks for the project
  • Do something with the workflow instances.

On Reactivation:

  • Recreate all user tasks for the project
  • Reverse whatever was done to the workflow instances on archival.

While archived:

  • Prevent modification of project except for reactivation.
@FyreByrd FyreByrd added the svelte-rewrite Issue for the S2 upgrade to Svelte label Feb 13, 2025
FyreByrd added a commit that referenced this issue Apr 2, 2025
FyreByrd added a commit that referenced this issue Apr 3, 2025
@FyreByrd FyreByrd added enhancement New feature or request post-deployment Changes to make after deploying S2 and removed svelte-rewrite Issue for the S2 upgrade to Svelte labels Apr 4, 2025
@FyreByrd
Copy link
Author

FyreByrd commented Apr 4, 2025

The current behavior matches S1. We will want to change this later probably

@chrisvire chrisvire added svelte-rewrite Issue for the S2 upgrade to Svelte and removed post-deployment Changes to make after deploying S2 labels Apr 4, 2025
@chrisvire
Copy link
Member

chrisvire commented Apr 4, 2025

This seems to be an important enough enhancement that we are going to include it in S2. Let's keep this simple.

On Archival:

  • remove user tasks

On Reactivation:

  • reassign user tasks

It seems like we can use the same code when a project is assigned to another person. If the project is in the archived state, then no one is assigned to it.

At the moment, I don't think we need to worry about preventing modification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request svelte-rewrite Issue for the S2 upgrade to Svelte
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants