Automation rule not appearing in Tasks

[Bilal Khan]

So I created a simple automation rule for re-occurring events. I just want the task to be re-created 1 month ahead after it transitions to "Done" but after creating the rule and publishing it, it cannot be attached to the task as you can see it says "No automations available". If I go inside Manage rules, I'll find them there but how can I link a rule to a task ?

[Bill Sheboy]

Hi @Bilal Khan -- Welcome to the Atlassian Community!

For a question like this, please consider posting images of your rule and the audit log.  That will provide context for the community to offer suggestions.  Thanks!

Until then, what is the trigger type for the rule?  Only rules with a Manual trigger show up in the list from the issue view.

For the use case you describe, I expect that the trigger is on Issue Transitioned rather than Manual.

Kind regards,
Bill

[Bilal Khan]

Hi @Bill Sheboy Thank you for the prompt response :)

The rule itself is fine and straight forward but I just realized what the problem is. This platform has not given us the ability to link rules with Epics/tasks/subtasks.

The rule automatically triggers when the condition is met but this is not good for me as I want only some particular issues to trigger the rule. It would have been fairly simple if the option to link rules to issues was there (no brainer)

Now I am guessing for my particular case I would need to somehow target specific epic or task for the rule to work.

So here is the rule and what I want to do is figure out how to target the trigger. Creating a new rule asks for Trigger but no option to target specific issues.

Here is the audit, I had created a new issue under another epic and closed one of the tasks to "done" and my rule triggered and that's when I found out what the problem was. So it works, just not the way I want it.

[Bill Sheboy]

Thanks for that information!

How do you know when you want the rule to run?  For example, is there a specific value in a specific field that you look for?

If so, you could add a condition after the trigger to check that field/value and then the rule would meet your use case.

[Bilal Khan]

I mean I wouldn't even need to make an automation rule if the simple option to have re-occurring events existed. Our case is very simple, we have stuff to do monthly and yearly, once this stuff is addressed and 'closed' I wanted Jira to recreate the issue 1 month or 1 year ahead rather than me manually cloning the issue and changing the dates.

I see where you are going with this, but again this is silly if I have to "look" for specific events to make my automation trigger for specific task. Solving the issue by making the problem more complex is not the idea for a good tasks management platform.

The triggers are the problem not the condition, they are very limited and of course since it is designed this way, no option to focus or isolate to a specific task. 

Anyways thanks for the help and hope other people who face the same issue will not have to keep searching the internet for answers. Hope the owners of this platform decide to actually implement re-occurring tasks feature or link automation rules to issues directly avoiding the need to isolate by looking for events to trigger. Turns out you can buy such modules from the marketplace.........now it all makes sense ;)

[Bilal Khan]

Guess this is the correct answer here:

Buy Recurring Tasks for Jira Cloud from marketplace or if your whole project is ok with the rule that you created then its fine. If you have multiple projects and need to isolate your rules, you will be making complex triggers or conditions.

If you want to open the door, you just need to reach out with your hand, twist the door knob and open it. But in case of Jira, you need to first sanitize your hands, wear gloves and THEN reach out to the door-knob to open it. (sorry for bad analogy pun intended, read the whole topic for context.)

Have a great day !