Via the backlog. Open your backlog's epic panel: Go to your project's backlog > Click the Epic dropdown filter > Click the Epic panel switch: Then select an epic and click + Create issue. Pro tip: Here you can also drag-and-drop issues from one epic to another. Hold Ctrl (Windows) or Command (Mac) to multi-select.

This makes it easy to keep track of the progress and status of your epic. Jira Epic vs. Task. Jira tasks are used to plan specific tasks that would take ~1 day for the team to complete. As each task is completed, the team will edge closer to completing the overarching theme of the project; the Jira epic. Features of a Jira Task:

2 rules: create the epic/stories in one rule and the sub-tasks in another. rule-A: create the epic, and when creating the stories add some field value to check. rule-B: triggered on issue created, check the condition for the field value you set in rule-A, and then create the sub-tasks. Please note: in rule-B, select the option "Allow rule

Epics and Features are higher level containers. User Stories and Tasks are more sub-level components. Epics can DIRECTLY be broken into User Stories/Tasks (aka backlog items) Epics IDEALLY need to be broken down into Features. Features can be broken down into User Stories / Tasks / Backlog Items. These tasks / stories are what fit into SPRINTS.

Under Jira GreenHopper (v6.0.6) there is a new feature. Jira > Agile > board > Plan, drag and drop the Story Issue onto the Epic. Using an old view, navigate to the story page. There should be a Epic Link field. Clicking on it and changing the value of it, should move story to the appropriate Epic.
Unless otherwise noted, the timeline view in Jira Software is the same for both company-managed and team-managed projects. The timeline is where you can create, manage, and visualize work from a board. Timelines are useful for planning large pieces of work several weeks or months in advance and planning large groups of stories.
Khadhar Mohaideen Oct 08, 2018. I have a requirement where we want to introduce Features as an issue type with the hierarchy of Epic --> Feature ---> Story ---> Sub-tasks., where we should be able to link Features as children of Epic and Stories as children of Features (with a filed similar to "Epic Link", such as "Feature Link" which links Adding subtasks to an epic upon its transition. Osama Al-Areky Oct 19, 2023. Hello, I would like to automate the addition of new sub tasks to an epic once this epic is transitioned, for example: an epic is transitioned from to do, to on going, then auomatically subtasks are created and added to it. I tried different ways to create a rule, but 2 Answers. No, it's not possible the way you want. I suggest the most common approach and that's to use Epic -> Task/Story -> Sub-Task hierarchy. The Sub-Task is the smallest task in Jira and it doesn't make sense to have any further sub-issues. Moreover, (User) Story is bigger piece of delivery than a Sub-Task. pxqq.
  • 3s9u6dd8fz.pages.dev/378
  • 3s9u6dd8fz.pages.dev/419
  • 3s9u6dd8fz.pages.dev/29
  • 3s9u6dd8fz.pages.dev/54
  • 3s9u6dd8fz.pages.dev/409
  • 3s9u6dd8fz.pages.dev/247
  • 3s9u6dd8fz.pages.dev/425
  • 3s9u6dd8fz.pages.dev/283

    • jira convert task to epic