Hi There,
I Subtasks on the stories .
I am looking for a Automation Rule which track Stories that spill over into the next Sprint, ensuring that any Sub-task that isn't completed gets marked as Spillover = Yes. when the sprint is closed.
Hi @Vishal Biyani Thank you so much. If the subtasks is NOT DONE, the issue filed Spillover should be updated as YES and if the Subtask is DONE the issue filed Spillover should be updated as NO.
Can you review and correct
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
in that case in Issue matches JQL use issuetype in subTaskIssueTypes()
Then add another if Issue matches JQL condition:
check statusCategory = Done
then edit issue fields to set Spilled Over = No
Then add another if Issue matches JQL condition:
check statusCategory != Done
edit issue fields to set Spilled Over = Yes
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.
Can you make the change and share the screen shot of what you have done?
if you hit an issue, I will be happy to help. However, for your own learning, I encourage you to try this out yourself first
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.
I think what you can do instead of having 3 if condition,
in 1st condition, use issuetype in subTaskIssueTypes() and statusCategory = Done
then edit issue
in 2nd condition, use issuetype in subTaskIssueTypes() and statusCategory != Done
then edit issue
that will ensure that both ifs are evaluated correctly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have tried the above query but for subtasks not done its getting updated as YES. But for subtasks with are done Spillover filed is not getting updated.
Kindly review and suggest
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
can you share the log of your automation execution
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.
2nd JQL condition shows the issues are not matching Done criteria. Looks like all the subtasks are matching not Done criteria.
Can you check if there are any sub tasks from above list that were in Done statusCategory?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi @Vishal Biyani
This automation of updating spillover field is working for subtask which are DONE , its not getting updated for Subtask which are not done. Could you please assit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think what you can do is, click on Add Component
Add same Branch for Issues in sprint
move the 2nd if and edit condition, in that branch.
This should work in my opinion
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.
Register nowOnline 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.