Mar 03, 2017. That is correct - subtasks are useless in Scrum planning and just waste space and make noise. A subtask always belongs to its parent, and that parent can have an Epic, which then implies that the sub-task is inside that Epic. But there's an oversight in that the subtasks don't actually inherit the information internally.
Unfortunately, as you see, this is not available natively in Jira. However, the Epic Progress gadget exists, and it's available in the Dashboard Hub for Jira – Custom Charts & Share Reports app, which is developed by my team :) It has two view types, List View (left) and Extended View (right). This is just one of the nearly 100 advanced
But you can still use this approach for any kind of project in Jira, making use of specific, readable, actionable epics to effectively deliver valuable increments of work. More Than a Name. While I do revel in epic naming, just as important is adding a clear summary to each epic in Jira, detailing what it is meant to accomplish.
Step 2: Use epics as objectives and issues as key results. Before listing your OKRs, there are a few details you need to customize. For non-Jira admins, you can use Epics as Objectives and Tasks as Key Results. But if you’re a Jira admin, you can simply rename Epics to Objectives under Issues > Issue Types.
Make sure you are using the same terminology used in the Epic. For example, in the Epic, I referred to a "nutritionists space", so bellow I'm using "space" as well, instead of "account" or "experience". Example of good release names are: Nutritionists space MVP; Gamification for patients iteration 2; Improvements to the patient website speed
Epics are supposed to represent a large piece of work that you are breaking down into little bits or manageable work (stories, but in Jira, use any issue type you want). These stories might need to be done by different teams, or held in different Jira projects.
. 156 348 153 261 234 205 366 385 237
jira when to use epic
