User Stories and Tasks

[Jason Chayer]

Kind of stuck, maybe. 

We have our Jira setup where our frontend and backend teams share one project. Within that project, we have multiple features being built out. With this, we are using Epics as the new feature and then have user stories associated to that epic. However, I am needing to create tasks that are related to each user story. I do not want to create subtasks because I need our SQA department to be able to test each task and write up any pre-release issues against those. Which is why I am not creating subtasks. 

Does this seem like the best approach?

[Mirek · Accepted solution]

Hi @Jason Chayer 

There could probably couple of solutions that might work. 

I think that there is nothing wrong with having multiple projects and linking things together. So you can have one view of requirements / new features (as epics and stories) then in a different project have other tasks that would be linked to the stories.. You can have one or multiple boards that would be used by different teams.. 

If you add automation to that you can have a quite good process of creating automatically some test tasks on specific workflow step or any other condition that is met etc... 

[Jason Chayer]

@Mirek That does make sense. However, this will all live in one board. So, the Project is at the Epic Level, and then we have Stories (User Stories) associated with that Epic. 

My thought is to have the User Story and anything that is related to that User Story be created as a task. I can then link any of those tasks to that User Story. The idea then would be have QA test the tasks and then one last pass through on the User Story itself once all the Tasks have been completed.

Any subtasks I would create under the Tasks if it is determined.