Answer accepted. @Aline Chapman It is possible to rename "Epic" issue type to "Feature" in Jira Cloud via Administration->Issues->Issue Types->Epic; click on three dots, which shows "Edit". In order to do that one should have Jira Admin access. Renaming is a global change (Configuration), it would impact all Jira projects in that Jira Cloud 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.
The solution I came with: Do a Bulk Change -> Move & select the SubTasks you want to fix. Convert them to Tasks using the bulk move, edit / bulk edit them to delete the epic link, then Bulk Move them back to SubTasks. You'll have to select the parent task when you convert them back to SubTasks so best to do this one set of SubTasks at a time.
How to create an epic that should contain stories which should contain tasks using python-jira. PAT Jun 28, 2020. Writing a script in python using python-jira library to convert nested dictionary to jira issues where the epic should have stories and the stories should have tasks where the details for each are in a nested dictionary.

A specific set of Epics and/or Tasks, or any other Issue Type. The Board Filter controls what is shown on a Board. For example, you could mark all your Epics/Tasks with a specific label, then filter for this label on the board to exclude all "other" Issues; A specific set of Statuses - or a subsection of one Workflow - using the columns settings.

If we create stories, tasks and sub task from the epic all these tasks will be displayed correctly in the board under the swimlane. Also if we use the default filters (by user). However, we create a new story or a task and then convert it into a sub task, which will be related to a story or task, which has a epic link.
lX9VSpZ.
  • itvwerx8h1.pages.dev/102
  • itvwerx8h1.pages.dev/147
  • itvwerx8h1.pages.dev/349
  • itvwerx8h1.pages.dev/22
  • itvwerx8h1.pages.dev/212
  • itvwerx8h1.pages.dev/145
  • itvwerx8h1.pages.dev/128
  • itvwerx8h1.pages.dev/34
  • itvwerx8h1.pages.dev/174

    • jira convert task to epic