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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are trying to create a rule that aims to transition issues from the TO DO column to the next column if the values in some custom fields are not null. When we try turning on/publishing the rule we see the following error:
The rule has been configured with components that require issues to be provided by the trigger. To run these components you must add a branch for this sprint or JQL. The following components require issues: Issue condition, Transition issue
Does anyone have idea of what is happening or what we're missing?
Hi Allan - Welcome to the Atlassian Community!
Can you give an example of exactly what you are trying to do? I am having a little trouble understanding exactly what you are doing.
Also, can you include a screenshot of the current rule you have?
Thank you for replying. We have a next-gen project in a scrum configuration.
What we would like to do is that when a sprint is started all of the issues that are automatically added to the backlog to be evaluated and based on whether three custom fields have a value, i.e. aren't null, then they are automatically transitioned to the next stage/column in the work flow.
Below is the automation rule we're attempting to configure and publish and the error we receive.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the explanation.
Try adding a Branch rule (the purple one) and select Issues in the sprint for the second component (right after When Sprint started).
The put all of your conditions under that and see if it helps you.
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.
Great! Glad I could help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Allan_Ditzel maybe you can share a screenshot from the solution. I'm facing the same issue and I'm currently not working with branches. So I'm not sure if the suggested solution applies to me.
Thanks in advance.
Update: I solved it via the Branch "For issues in this sprint". Maybe this will help someone.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome thanks!
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.