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
Next: Root
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
HI community ,
I have an issue creating an automation .
I need to create a scheduled issue ( every day ) with a specific summary in the specific project, and transition that newly created issues to " To do" status .
When applying the transition , I get this error:
Sona,
The other commenters are pointing out that the "Transition Issue" component needs to run within a section that refers to one or more issues.
Even though the "Create Issue" component ran right before it, your "Transition Issue" isn't nested in a branch or section of that component. Instead it's running under the Schedule trigger itself, which doesn't mention any specific issue.
So, you have to use the Branch Rule / Related Issues component, and write some JQL that goes and fetches the ticket you just created. Then you can put the "Transition Issue" component in the sub-components section of that branch.
Here's an example of my own, yours will look something like this (although the JQL will need to change). Notice I'm trying to match on the summary text, and also looking at tickets created since yesterday.
Thank you so much for the answer . Will give it a try , though already sure it is what I looked for .
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey all,
I was able to accomplish a similar automation by branching off of 'all created issues':
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sona,
Can you share your complete rule?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So you need to add a JQL statement so it knows when issues to use.
So which cards if they exist in the scheduled trigger will cause cards to get created. You need to have a condition more or less.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear John,
In the scheduled trigger the action is to create an issue every day at 9 am in the specific project with the same summary. So there is no card till that , and I need an action to move this newly created card from backlog to -to do. So what jql do I need to write If there is no predefined card ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When you are creating the card, are you populating the Component field? It needs certain values in that field fo do the Transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.