Best Practices for Jira Scrumboard

[Zack Lindberg]

I am wondering what others are doing configuring their scrum boards.

Currently our team has the user story as a Swimlane and the associated subtasks are underneath. 

The subtasks move through the workflow until Done. That does not update the parent Story status.

I would like the board to show stories move through their own workflow (To DO, In Dev, In QA, In UAT, Done) as well. 

What are others doing to achieve this. Do you move the subtasks through their workflow then manually update the story status on the board where applicable?

[smithclarkson001]

I am transitioning from Pivotal Tracker to Jira and as is perhaps no surprise I am totally underwater here. Trying to rapidly understand and leverage all of the modules of Jira for our project. Couple of questions:

1. In a Scrum project what does the work flow do for me?

2. Assuming I want or need a workflow, how do I make my board look like my workflow?

3. In Jira my developers will change a status by dragging and dropping the story from board to board, is that correct?

Thanks in advance for you guidance on this. If anyone has a 'Quick Build for your Scrum Project' with Jira that they would recommend please send it my way.

I am transitioning from Pivotal Tracker to Jira and as is perhaps no surprise I am totally underwater here. Trying to rapidly understand and leverage all of the modules of Jira for our project. Couple of questions:

1. In a Scrum project what does the work flow do for me?

2. Assuming I want or need a workflow, how do I make my board look like my workflow?

3. In Jira my developers will change a status by dragging and dropping the story from board to board, is that correct?

Thanks in advance for you guidance on this. If anyone has a 'Quick Build for your Scrum Project' with Jira that they would recommend please send it my way.