Hi @Shehrooz Ahmad -- Welcome to the Atlassian Community!
When you read over that error, you note it indicates there are components in the rule requiring issues, and there are none. That is correct...
Your trigger is sprint created, and sprints initially have no issues so none are available. If you expect there to be issues assigned at the time the sprint is created, you could use a JQL branch or Lookup Issues action to find issues associated the newly created sprint.
However I suspect that trigger will fire long before issues can be assigned, so would you please describe the problem you are trying to solve with the condition testing Issue Type? Knowing that may help the community to offer suggestions to help. Thanks!
Kind regards,
Bill
Hi Bill, I actually want to create issues automatically once I create a sprint but don't know what I'm doing wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for clarifying! If you remove that first condition test (after the branch) you should be all set to add issues, and any subtasks under them, as needed.
For example:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.