create subtask -when issue moved into active sprint or in sprint when it starts

[Jacob Goldman]

Hi- 

I want to create an automation that automatically creates a placeholder subtask when either:

1) the issue is story/task and is in the sprint when it starts

and

2) the issue is a story/task and is moved into the active sprint

We are trying to enforce always committing code against a sub-task. Automations I've experimented with are resulting in a sub-task being created even if I moved a ticket into the future sprint while I am exploring prioritization.

I recognize that a subtask will get created one way or another, but i am curious how this can be done.

Thank you,

Jacob

[Andreas Hinterplattner]

.   

[Alexey Matveev]

Hello,

When you move an issue to the Published status, you need to set the Resolution field. You can do it by putting the resolution field in this transition or add the Update Issue Field post function to this transition and set the resolution field in this post function.

[Andreas Hinterplattner]

Hi Alexey,

Thank you for your quick response. I saw that the "The Resolution of the issue will be set to Done" function was missing from the transition. I went ahead and added this post function (update issue field - resolution - done).

Now the all published issues show up under done issues - great! However, they're still showing up under open issues as well - not so great. Why's that?

Thanks a lot.   

[Alexey Matveev]

You can find more detailed explanation here:

https://confluence.atlassian.com/jirakb/resolved-issues-appearing-in-open-issues-filters-696386344.html

Kindly make sure that the status of the issue is of the done category.