Status of a user story that contains FE and BE tasks

[enji istanbouli]

Hello, we are creating in my team one user story which contains both FE and BE tasks. my question is, while having one of the tasks in progress, what should ideally be the status of the US? Logically it's in progress, but this is causing confusion. do you have any better way to handle this kind of user stories ? 

[Nic Brough -Adaptavist-]

The question is here is quite simple - is there one story here or two?

If there's two stories (one for FE, one for BE), it's simple, there's two stories, so you split the issue into two.

If there's only one story but it has two parts to handle separately, then create a sub-task for each.   There are three logical situations here, which match the status categories:

When both sub-tasks are to-do, then their parent should be to-do or in-progress (you can start the parent without starting sub-tasks)

When either of them are in-progress, then the parent should be in progress.  You don't start part of a story and leave the story as to-do, that doesn't make sense.

When all the sub-tasks are done, then the parent can be done.  But it doesn't have to be, it is possible that you could complete all the sub-tasks but still have bits of the parent to do

The only combination that doesn't make any sense is "Story = to-do, while one or more of its sub-tasks are in-progress or done (unless the 'done' is because we cancelled it)"