How are epics and tasks usually done in Jira cloud for project management and status update meetings? Do Sprints usually mean you just look at all your Tasks without the Epic to see what you're working on? Or should you look at Epics first and then look at their tasks to get a status? Seems like if you're looking at the kanban board all you see are "Task" issues and it seems messy and confusing because there's no context, and putting full context on every task might be over redundant?
Jira softwafre provides some project templates and workflows, but how to use and what the best practice is depends on your team and their engineering practices.
For example, scrum, large scale agile, waterfall, Kanban, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.