I am trying the following
When Epic is created with "Automation" in summary
Then -> Create a task
Ideally i wanted to create the task with Parent as the Epic, but this kept failing. Hence to make things "simpler", i decided not to add the additionl action of adding a "Parent".
Irrespective of the fact that i add the parent or not, the automation rule always fails at "Creating Issue"
## Rule
## Audit Log
I am quite unsure as why the task creation fails.
@Deven Patel I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-987755
I don't know exactly why you would be seeing this error, but I think it would be best for us to have this support ticket so that we can more closely look at your environment.
Andy
Thank you for the support and prioritizing the issue. However, i am not exactly sure by "we can more closely look at your environment."
Would this need any further information or action from my side? I am neither the administrator nor do I have any admin privileges for my company's Jira instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I understand that. That is why we have included a site-admin on the support ticket. It might help if you can provide details such as the name of the automation rule and if it is a project specific rule, which project does it exist in. Adding those details to the support ticket can help our team to better understand where this problem is happening.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Automation Rule is project-specific and called "Automation Test Rule". The project name is WTCW, as you can see from the screenshot.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is the second post I have seen where a user has mentioned getting such an error in an Automation Rule when trying to Create/Clone an issue.
I am not experiencing the same problem in my Free Jira Cloud instance.
I'm going to flag this post and the other one for an Atlassian Team Member to review.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good call, as there have been an increasing number of these for the last few days.
There is a pending scheduled maintenance this weekend, 7 April, and so I wonder if something is updating earlier than planned: https://jira-software.status.atlassian.com/incidents/xckcr2snrjx0
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you catch the news at Team ‘25? With Loom, Confluence, Atlassian Intelligence, & even Jira 👀, you won’t have to worry about taking meeting notes again… unless you want to. Join us to explore the beta & discover a new way to boost meeting productivity.
Register today!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.