We're using a kanban board but we're unsure how to represent stories that we break down into subtasks. Do we create subtasks under the parent story and move those subtask issue types through our workflow or do we create task issue types that we move through our workflow and just close the story?
It's unclear how these two methods impact things like cycle time and the documentation doesn't give any guidance. Does Atlassian recommend a particular way? What does your team do?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs