Agile teams use epics to track larger sections of work composed of smaller tasks, bugs and user stories. Jira uses the suggested epic issue type to power other features in team-managed projects, like roadmaps and reports. To use these features, you must use the suggested Epic issue type (and avoid creating your own custom issue type called "Epic").
If you have a sub-task that you want convert to a task, you can: Change your board view to make sub-tasks visible with Group By. Select the sub-task you want to convert. Under the menu at the right side, select Move. Change the type from sub-task to task. Select Next > Next > Confirm to make the change. Acknowledge when done.
Cody Wikman Jul 29, 2022. @Sama Mohamed When viewing the Backlog click to show the Epic Panel. When the epics are visible you can simply drag your tasks to the epics to assign them. You can do this with multiple tasks if they are highlighted. Multiple tasks may be selected by holding shift or control/cmd.
The goal for my automation rule is for a user to edit the Epic Link field on a ticket and then it will automatically add a parent/child link between the Epic and the Story or Task. Here is the flow of my current build but I am having issue with choosing the right trigger. I would like it to trigger the rule when the issue field "Epic Link" has
Oct 25, 2018 Navigate to the Task and click on he edit button. On the edit screen you will see a field called as Epic (if not available reach out to your admin to have it added). you can used this field to search for the epic you want to associate with the task. Like • 2 people like this Amit Anand Oct 25, 2018 Many thanks that has worked! Like Please try, "def value = issue.getCustomFieldValue (cf)" it should work now. I tried this, however this picks the value from the story and maps it back to story. My requirement is to have the custom field value taken from epic and mapped to story during issue creation. Probably need to setup a connection between epic and story before mapping

Within JXL, enable the issue hierarchy. This is a one click action. You can now easily select the epics and their children (just like you would select cells or rows in Excel/Google Sheets), right-click them, and invoke the "bulk edit" process via the context menu. This is how this would look in action: (In the future, we may add a "move

Meet the powerful Epic Progress gadget. There is an Epic Progress gadget, and it’s available thanks to Dashboard Hub for Jira. This gadget displays the progression in the completion of a particular group of epics by different estimation statistics. Get the insights you need with a well-designed user interface and great customization. click on the three dots above the Sub-Tasks list and make a bulk-change; select all Sub-Tasks; now choose the correct Story; execute the move operation; your Epic with child Tasks has become a Story with Sub-Tasks; Now you can re-use the dummy Story for other Epics, which needed to be converted, too, but you have to do this for each Epic First, change the issue type from "task" to "story". If they're configured the same way, then you can just edit the issue type directly, but if they're not, you'll need to use the "move" function to walk through all the checks that the data will be compatible with the Story config. Second, edit the "epic link" field - you'll be able to change You can pull a list of all issues in an epic with the following JQL, by the way: "Epic link" = ORDER BY Due DESC. EPIC-123 would be the issue key of any open Epic you want to check. And ORDER BY Due DESC would make sure the issue with the latest due date appears at the top of your list.
Click on “Issues” in the top menu. Choose the advanced JQL search modes. In the search bar of the , type the query to filter issues by a specific epic. For example: "Epic Link" = EPIC-KEY, where EPIC-KEY is the identifier of your epic. You can refine the search by adding more criteria, such as status, assignee, or due dates.
@Pramodh M update: I followed instructions to rename "epic" to "feature". worked as expected. We changed it back to "epic" in our test environment, as conducting Align integration testing. After reverting the change back to "epic", we found that the the "epic name" not showing in the epic link field of a child story.
As the name implies, epics usually represent a significant deliverable. In the backlog, you can filter by issues belonging to a single epic. Example: Character movement update; In this example, the epic encompasses the story of adding joystick support, as well other stories, tasks, and bugs in an overall initiative. It might look something like
Yes you can copy the values of fields in an Epic down to linked Tasks by using Automation for Jira. However, what type of project is it - Team-managed (Next-gen)? Or Company-managed (Classic Software)? Thank you - will check the solution ( Automation for Jira). You should be fine then with the Company-managed project.
Select the Cogwheel symbol from the drop-down menu. Select Projects. Choose the project that you need. Select Permissions from the drop-down menu (left menu) Select the Actions option from the drop-down menu. Select Permissions to Edit. Look for the ‘Delete problems’ permission and click the ‘add’ button next to it.
If you were using a Company Managed project then you could use Issue Linking to link the additional Epics to the issue, and you could add Linked issues as a field to display in the cards. The result would look like this. CKB-2 is the linked issue. "Epic 2" is the epic that has been designated as the parent.

In order for the epic labels to appear on a board, those epic issue types have to appear in the search results of the JQL filter in use on that board. For example: If your filter looks like this project = abc and customfield=xyz order by rank asc. but your epics exist in different projects, you can change the filter to look like this

Date ranges: Hover on an epic to view its date range. Drag its left and right edges to adjust the date range, or click the epic to open it and edit its details. Manage epics on the roadmap; Also, make sure that on Project settings > Issue types > Epic that the fields were added to the context fields. Regards, Angélica .