Is there a way to have a subtask keep the same status when the Story for the sprint is closed.

[Cor Slagmolen]

Let me explain the situation. Our deployments to Acceptance and to Production always take place a few days after the conclusion of the sprint. For some issues, such as hotfixes, the complete flow may take place within the sprint.
We have the statuses:
New
In refinement
Ready
In Progress
In Review
In test
Ready for Accept Deployment (means tested successfully)
In Acceptance
Ready for Prod Deployment (means successful UAT)
Done (Means In Production)

To ensure that all story points are Included in the velocity are the statuses:
Ready for Accept Deployment
In Acceptance
Ready for Prod Deployment
and Done are all part of the last column of the sprint board (Scrum).

To monitor the flow after the sprint, a separate kanban board has been created with the statuses and columns:
Ready for Accept Deployment
In Acceptance
Ready for Prod Deployment
and Done.

The problem now is that a subtask that must be executed when the story is "In Acceptance" prevents you from closing the story during a sprint change. So I want subtasks to keep their status at the end of the sprint. Hopefully this is clear... Thanks in advance for the feedback.

[Trudy Claspill]

Hello @Cor Slagmolen 

When you say that the subtask must be executed, do you mean that subtask is in a status other than one that is mapped to the farthest right column?

If so, the answer is no. To finish the Complete Sprint process, for all the standard level issues in the right-most column that have subtasks those subtasks must also be in the right-most column. Otherwise the standard level issue is not considered "complete" because there is work (sub-tasks) that are not "complete".

[Cor Slagmolen]

OK. so subtasks should have the same statuses as the story. Or create a specific flow with a status "Subtask In progress" for the subtasks and add it to the last column. Would that work?

[Trudy Claspill]

The subtasks don't have to have an identical status to their parent. But, if the parent and subtask use the same workflow, then for the parent to be considered complete and for the sprint to be able to be completed the subtasks have to be in a status that is mapped to the right-most column of the board.

You could create a separate workflow for the subtasks, and give them a status that you can map to the right-most column.

However, before doing that in your production project I would recommend that you make a test project with a copy of the workflows and workflow scheme, with boards configured in the same way, and with some test issues and experiment with the workflow changes. Confirm that the changes work the way you expect in the test project and both test boards before you make changes to your production project