-
Notifications
You must be signed in to change notification settings - Fork 208
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
Delete tags before adding new ones #131
Comments
Hmm, this brings up a few of thoughts:
|
Yeah, I vote for the UDA approach in number 3, but number 2 would work as well. |
I ended up going with approach 3, fyi. |
The way I use bugwarrior is that any task created by bugwarrior, is solely managed (updated/deleted) by it. I don't make any modifications to those tasks since they could be overwritten the next time bugwarrior-pull runs. Instead, I have a simple script that will clone a task, strip its foreign ID, and mark the Bugwarrior task as dependent on my new one. I use my new, cloned task for starting/stopping work (which I use for time tracking), adding/modifying annotations, tags, due dates, etc. When I'm done, I have a helper script that will close out the remote task and my local task. All of that is to say, that's why I felt that clearing out all tags from the BW-managed task is OK, but I get that my workflow is probably different from most people's. |
Closing this way after the fact. :) |
Currently I'm mapping issue labels in the activeCollab service as Taskwarrior tags. Let's say an activeCollab issue comes in with the label
ON_HOLD
. Bugwarrior creates a TW task with this tag. Then the activeCollab issue gets changed toIN_PROGRESS
. On the nextbugwarrior-pull
we now have a task withON_HOLD
andIN_PROGRESS
tags assigned.What do you all think about having Bugwarrior delete any prior tags before assigning them on a task update? /cc @coddingtonbear @ralphbean
The text was updated successfully, but these errors were encountered: