You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Triggering a Jira automation rule outside of an issue ist very (too) limited for both development and production use. What I'd like to see:
Scheduled triggers are OK, but not everything is scheduled.
Hi @Arnd Layer
Thanks for sharing these suggestions! Can you share any more detail about how you might use a trigger from a URL or Confluence page, to help us understand how we can support this use case?
If you’d like to chat to the Automation team, we’re always happy to learn more about how you’re using Automation and how we can improve - feel free to book a time that suits: https://calendly.com/cgavey/automation-feedback
Thanks again for taking the time to share this feedback.
Hi @Charlie Gavey ,
why would I like to trigger an automation rule from URL / Confluence page?
This would be a rule that collects and provides information, e.g. send a list of issues via email or chat. Today I would use a scheduled trigger, which potentially creates a lot of unnecessary emails and many users already treat emails from Jira similar to SPAM.
A project manager could trigger the sending of such an info when necessary.
A Confluence page could easily contain such a URL while Jira itself does not really have a convenient place. Theoretically one could use a sidebar link, but one may have several such rules.