How to define automation to move story from backlog to current sprint

[Paul Merrill]

I've got an automation working that creates a new story when any story is transitioned from In Process to In Review. The creation of the new story works fine, it's created in the backlog but for some reason I can't make it move to the current sprint. The rule seems to fire but the story in the backlog doesn't move to the current sprint and there are no error messages.

[Paul Merrill]

Bill,

The "rule indicates, Create a new Story in Same Project and the next step says, And move issue to board (the move issues doesn't work as expected). What I hear you saying is I may not need the Move Issue step but I can do it all in the Create a new Story step?

If you can tell me precisely how to fix that would be very useful as I'm new to this stuff.

The create story step looks as follows:

[Bill Sheboy]

In the Create Issue action, you may use the "Choose fields to set" dropdown list to select the Sprint field.  

In that field, select current, active sprint for your board.

[Duc Thang TRAN]

Hello @Paul Merrill 

I seem you need to put another action (Edit issue)  to add a value of Sprint field.
If you have only one actif sprint, you can chose directly the choice "Active Sprint". 

Hope this can help 

[Paul Merrill]

[Paul Merrill]

To me this looks like it should work but the story remains in the backlog and is not put in the sprint.

[Bill Sheboy]

Hi @Paul Merrill 

When you create the new issue, do you set the Sprint field to the "active sprint"?

If you did and it is not working, please post an images of the Create Issue action and the audit log details showing an example where the rule ran and the field was not set.  Those may help to explain this symptom.

Also...adding a issue to the active sprint will change the scope of the sprint, altering the team's plan and potentially impacting changes of meeting the goal.  What has the team discussed about using this approach and potential risks?

Kind regards,
Bill