Error when using label filter in task reminder rule

[Dag Atle Stentad]

I want to create a rule that sends reminders for tasks that are about to expire. I have managed to get this to work fine. However, I want to extend the rule to only include issues that contain the label: task-reminder. When I add this, I get an error message.

I also tried creating a rule with a branch using CQL: label = task-reminder, but for some reason, ’m not allowed to put a task branch inside another branch.

Any suggestions on how to make this work only for pages with the correct label?

[Bill Sheboy · Accepted solution]

Hi @Dag Atle Stentad 

That error indicates there is no page present for the condition to test.  The branch is over Tasks, and so its parent page is not available.

I believe the only way to do what you ask would be using the REST API with the Send Web Request action a couple of times:

• for the Task, get the page ID with the REST API
• for the page ID, get labels with the REST API
• check if your label is present with a condition on the web response

Kind regards,
Bill

[Dag Atle Stentad]

Thanks for your reply.

I was hoping I could use Automate, but I guess I'll have to roll up my sleeves and build it with the REST API.

If it were possible to include one branch within another, Automate would be much more powerful and could handle more use cases. Do you know if there is a feature request for this that we can vote on?

[Bill Sheboy]

There was a Jira Cloud suggestion that included nested branching, which is marked as "fixed", but the branch-nesting was not added: https://jira.atlassian.com/browse/AUTO-67 

Instead, only some conditional-if nesting was added, and in my opinion, that feature is neither reliable nor easily maintainable in rules.

I recommend adding a new suggestion with only that feature, perhaps referencing the original one.  Noting your scenario may help to focus the topic.

[Henning Stoll]

Hello @Dag Atle Stentad ,

my view on this matter is that youre applying the condition at the wrong position in the automation. Try adding it after the branch and before the action. Because otherwise jira runs into a sequencing error since its trying to apply a condition before identifying the ticket.

Best regards

Henning

[Dag Atle Stentad]

Unfortunately, you get the same error if you move it.