Answers.Body: <p>Thanks for sharing your problem.</p>
  <p>As you can see there are a few outstanding issues with tags: <a href="https://lab.civicrm.org/extensions/civirules/-/issues?scope=all&amp;utf8=%E2%9C%93&amp;state=opened&amp;search=tag" rel="nofollow noreferrer">https://lab.civicrm.org/extensions/civirules/-/issues?scope=all&amp;utf8=%E2%9C%93&amp;state=opened&amp;search=tag</a></p>
  <p>As you are probably aware CiviRules is open source like the rest of CiviCRM. That means that issues will be fixed in a number of ways:</p>
  <ul>
  <li>organizations run into bugs and get their own staff to fix them</li>
  <li>organizations run into bugs and pay a CiviCRM partner/developer to fix them</li>
  </ul>
  <p>So if you are in a position to either fix the problem or fund someone else fixing it that would be great! Most of the times issues do not get fixed without someone bearing the cost at some point, the power of open source is that the solution is then shared freely.</p>
  <p>On top of this CiviCooP sponsors a yearly 2 day sprint to fix as many as the issues as we can in 2 days. But there is no guarantee that the issue that is bugging you is on top of the list (although in this case it probably will be....). This sprint is going to be in the week of 10 May. Any sponsorship for an additional day will be welcome :-)</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-08T15:29:37.810Z
Answers.Text: I am aware of these options, but this is a case where something used to work correctly, then someone broke it. So why isn't that person responsible for fixing what they broke? Please understand from my "bio" that we are a small non-profit and I have no coding skills. Last year we contributed to a "fix" for another issue, funding most of the work. It didn't actually solve the problem, so we feel that we wasted our money. We are grateful for all the work people do on Civi, but please try to understand this end user's frustration. :-)
Answers.UserDisplayName: The Amateur
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-09T08:03:57.563Z
Answers.Text: I totally understand the frustration, and regression issues are doubly frustrating. Unfortunately the shop will not give me bread in exchange for gratefulness and I suppose that goes for lots of others too. To be clear: no one "breaks" things on purpose and there is almost never one person clearly responsible for a fix. I did not break it yet I am personally sponsoring fixing it in the first week of May. Wasting your money is not a term I appreciate in this context?
Answers.UserDisplayName: ErikH - CiviCooP
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-09T16:33:50.000Z
Answers.Text: I understand that no one breaks things on purpose. I wasn't suggesting that. I also wasn't suggesting that you specifically wasted our money. The fix we contributed to was unrelated to this and was paid to someone else. All I am saying is that we supported the work, but it didn't solve the problem. Sorry if I wasn't clear.
Answers.UserDisplayName: The Amateur
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-08T06:44:58.070Z
Answers.LastActivityDate: 2021-04-08T06:44:58.070Z
Answers.UserDisplayName: ErikH - CiviCooP
Body: <p>Using CiviCRM 5.35.1 with Drupal 7. Just installed the new CiviRules extension 2.23. I've been waiting for this because CiviRules has not been working with Tags for a couple of months and it has totally messed up our membership workflow. :-(</p>
  <p>Just tested the new version of the CiviRules extension (2.23) and some things are fixed, but not others. When <strong>changing membership status</strong> is the trigger, CiviRules does add the tags it should to the contact and does add the contact to the groups it should. :-)</p>
  <p>However, when <strong>adding a tag</strong> is the trigger, it still does not add contacts to groups or remove them from groups as it used to do. :-(</p>
  <p>Is anyone else seeing this?</p>
  <p>Thanks.</p>
  
Tags: <civirules><tags>
Title: Why is CiviRules not firing when the trigger is adding a tag?
ThreadText: # Why is CiviRules not firing when the trigger is adding a tag?
  
  (Asked by: username_0 on 2021-04-07)
  
  Using CiviCRM 5.35.1 with Drupal 7. Just installed the new CiviRules extension 2.23. I've been waiting for this because CiviRules has not been working with Tags for a couple of months and it has totally messed up our membership workflow. :-(
  
  Just tested the new version of the CiviRules extension (2.23) and some things are fixed, but not others. When **changing membership status** is the trigger, CiviRules does add the tags it should to the contact and does add the contact to the groups it should. :-)
  
  However, when **adding a tag** is the trigger, it still does not add contacts to groups or remove them from groups as it used to do. :-(
  
  Is anyone else seeing this?
  
  Thanks.
  
  **Tags:** civirules, tags
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-04-08. Score: 2
  
  Thanks for sharing your problem.
  
  As you can see there are a few outstanding issues with tags: <https://lab.civicrm.org/extensions/civirules/-/issues?scope=all&utf8=%E2%9C%93&state=opened&search=tag>
  
  As you are probably aware CiviRules is open source like the rest of CiviCRM. That means that issues will be fixed in a number of ways:
  
  * organizations run into bugs and get their own staff to fix them
  * organizations run into bugs and pay a CiviCRM partner/developer to fix them
  
  So if you are in a position to either fix the problem or fund someone else fixing it that would be great! Most of the times issues do not get fixed without someone bearing the cost at some point, the power of open source is that the solution is then shared freely.
  
  On top of this CiviCooP sponsors a yearly 2 day sprint to fix as many as the issues as we can in 2 days. But there is no guarantee that the issue that is bugging you is on top of the list (although in this case it probably will be....). This sprint is going to be in the week of 10 May. Any sponsorship for an additional day will be welcome :-)
  
  > **Comments:**
  > **username_0**: I am aware of these options, but this is a case where something used to work correctly, then someone broke it. So why isn't that person responsible for fixing what they broke? Please understand from my "bio" that we are a small non-profit and I have no coding skills. Last year we contributed to a "fix" for another issue, funding most of the work. It didn't actually solve the problem, so we feel that we wasted our money. We are grateful for all the work people do on Civi, but please try to understand this end user's frustration. :-)  
  > **username_1**: I totally understand the frustration, and regression issues are doubly frustrating. Unfortunately the shop will not give me bread in exchange for gratefulness and I suppose that goes for lots of others too. To be clear: no one "breaks" things on purpose and there is almost never one person clearly responsible for a fix. I did not break it yet I am personally sponsoring fixing it in the first week of May. Wasting your money is not a term I appreciate in this context?  
  > **username_0**: I understand that no one breaks things on purpose. I wasn't suggesting that. I also wasn't suggesting that you specifically wasted our money. The fix we contributed to was unrelated to this and was paid to someone else. All I am saying is that we supported the work, but it didn't solve the problem. Sorry if I wasn't clear.  
  
  ---
  
  