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!
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.
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events