1/29/2024 0 Comments Trello recurring tasks![]() ![]() I have a task that I want to create a recurring issue for every month. Let’s look at a quick recap of the use case. move it to Done), the Due Date of the cloned issue will always be in relationship to the Due Date of the original issue. The result is that no matter when you actually close the issue (i.e. The Monthly value will use plus 1 month, the Quarterly value will use plus months, etc. So, the Due Date is adjusted to be the Due Date of the original issue plus one week. In the example above, we are working with the Weekly recurring need. You will need to do that for each Recurring Need value that you use. In the next screenshot we will see what will the Clone action looks like?įinally, you will need to adjust the value that gets placed in the Due Date of the CLONED issue. But it won’t create the issue until the original issue is actually completed – i.e. This will effectively create the “recurring” issue. Next will be a series of IF conditions for each of the options in the Recurring Needs fields – one for Weekly, one for Bi-weekly, one for Monthly and so on.Īfter each IF condition, we will include a new action to clone the issue. This will allow any issue transitioning to Done on the project that has a value in the Recurring Need field to keep processing. We will also work off of the assumption that the issue will have a value for the Due Date.Īfter identifying the initial trigger type, we will add a Condition to check if the Recurring Need field is not empty. It will be based on when an issue is transitioned to Done. You can further control which projects it should be available for by adding a context with limited project names. The field would then be placed on the Create and/or Edit screen. I have called the field simply Recurring Need. As an example, I have created a Single Picker with the options of Weekly, Bi-weekly, Monthly, Quarterly, Annually, 24 Months and 36 Months. That might be a Radio type or Single Picker with a dropdown. While you could also achieve that using a Scheduled trigger and a Clone Issue action, you would need to create a rule foe each issue for which you wish to clone.īut what if we could accomplish the goal with a single rule, that fires consistently, but also in a flexible what?!?! Let’s explore how that can be accomplished.įirst, create a new custom field with controlled options. Or perhaps there is a need for more flexibility, such as cloning a particular card when it gets moved to Done. You can even base the trigger on JQL, if so desired, to cause multiple issues to be created based on other criteria such as Labels or Components. First, if there is a consistency aspect, such as a task is needs to be created on the first day of each month, or on the 15 th of the month, or both! This can be done by creating a simple a rule based on a Scheduled trigger. And there’s a couple of ways to go about that. Perhaps where this can be seen best is in the creation of recurring tasks. ![]() The second benefit is to reduce the overhead of administrative functions such as cloning or creating issues, auto-transitioning of issues, sending emails, etc. One of the primary goals of Automation is to provide consistent handling of user triggered events such as transitions of issues, field changes, issues created, or other similar things. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |