Skip to content

Conversation

@timdmackey
Copy link
Contributor

This task automatically removes specific order tag(s) when orders are closed/archived.

Canny Request Another low-hanging fruit. The code is almost identical to Untag orders when paid.

I'm wondering if this would make sense to fold into the first task rather than having a separate task? It would have a radio select to determine which event to act on (paid, archived, fulfilled?...). I don't know how task migration works though, so it might not be possible to add those options to a task that's already installed in stores.

This task automatically removes specific order tag(s) when orders are closed/archived.
@tekhaus tekhaus self-assigned this Dec 8, 2025
@tekhaus tekhaus self-requested a review December 9, 2025 20:39
@tekhaus
Copy link
Collaborator

tekhaus commented Dec 9, 2025

@timdmackey I agree that it might make more sense to have a single task to handle this for orders. When an existing library task is updated by adjusting any of the task options, merchants will not be able to update the task with one click, but it isn't overly onerous I think to install a fresh copy if the enhancements are useful.

If you decide to update the original, then I would also recommend doing a tag check on the order before running a potentially unnecessary tag remove mutation.

Copy link
Collaborator

@tekhaus tekhaus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me know what you decide on merging with original task.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants