At the right side of the search bar, select "list view". Then, add the column "Epic Link" > Click in Export > Select "Export Excel CSV (Current fields)" If you want to export all fields from your issues, including the Epic link, Click in Export > Select "Export Excel CSV (All fields)". In both options above, the relation between Epics and child
Export Jira data as CSV files. This method involves more manual work, and can potentially lead to multiple versions of your data that are tough to keep track of. Use Unito to export issues from Jira. Unito is a no-code two-way sync solution that can automatically pull Jira issues and push them to Excel, keeping everything in sync the whole way.

Once you’ve logged in to your Jira account, navigate to the project in question and click the global Create button in the top toolbar. In the resulting window ( Figure A ), make sure to select

But I noticed the following: When you have a Story ticket (which appears in the sprint board and backlog views) and convert it into an Epic (using the "Move" function), then magically the ticket still appears in the sprint board, now as an Epic. Weird thing is, that when you search for it on the Backlog view, it does appear as an Epic in the
Jira will never display the stories -under- the epic, which is very frustrating. But displaying the name of the epic link will do the trick. Realizing that the original poster certainly figured this out a year ago, but thinking that others might have the same question.
Select the Import from dropdown list and select the Jira project that you wish to import issues from. In the Jira-GitLab user mapping template section, the table shows to which GitLab users your Jira users are mapped. When the form appears, the dropdown list defaults to the user conducting the import. To change any of the mappings, select the
It contains a Jira epic burndown chart, but you can report only on one epic. It doesn't allow adding custom content or create a report across multiple epics. You can use the epic report inside Jira Software, but a more advanced tool to create a Jira epic completion report for all epics. To see the epic report in Jira: Navigate to a Jira project.
10 quick steps to translate Jira epic to SAFe feature. Start by installing the SAFe EPIC to Feature Translator from the Atlassian Marketplace. Once installed, the app will crawl for instances of “epic” and automatically translate to “feature.”. However, there are a few custom fields and issue types that are locked by Jira.
In Jira, how do I convert a story into an epic?Helpful? Please support me on Patreon:
The idea of spikes is to try to accommodate additional work that was not foreseen at the start of the sprint or it is perhaps the result of wrong estimation on a user story. Therefore, if the team deems necessary to add more work, the spike will provide the additional estimation points needed to complete the work in a given sprint.

Make a Jira Service Desk project in Jira It’s simple to set up a Jira Service Desk project: Step 1: Select Projects from the left-hand panel. To start a New Project, click the Create Project button. Give the Project a Name. Step 2: Change or use the default Project Template.

Note: running Jira Server 6.2 (I know, old) tl;dr Create task as regular, non-sub-task level, then do "convert to subtask". Epic Link will remain populated. I have tasks/stories with subtasks and just noticed some of those subtasks do have the "Epic Link" field populated, and so show in filters for "Epic Link = .", which is very nice.

If the Epics panel is not shown at the left of the screen, select Tools > Show Epic Panel. In the Epics panel, click the triangle at the left of the epic name to display the epic details. Drag the issue (s) onto the relevant epic. The epic will turn green (see Screenshot 2 ). The epic's name will be displayed on the issue as a coloured lozenge.

Step 1: Create a new epic in Jira Software There are three ways to create epics in Jira Software: the Timeline, Backlog, and Global Create issue button. When you create an epic, you'll need to enter the following details: Epic name - A short identifier for your epic. This will be used as a label on issues that belong to this epic.
def epicLinkFieldValue = issue.getCustomFieldValue (epicLinkField) //log.warn ("epicLinkFieldValue: " + epicLinkFieldValue) //To pass the epic issue key in string format. String TargetIssueString = epicLinkFieldValue. //To translate the epic issue key to ID.
Kanban and Scrum boards are just a visualisation of your filtered work - there is no way to convert a Scrum board into a Kanban board, but you can create a new board and visualise it. This is how to do this: Go to Boards > Create Board > Create a Kanban board. Select to create the board from an existing saved filter and click Next.
To clone an issue: Open an issue. Select ··· > Clone. Edit the Summary. Choose what to Include (if any). Select Clone. Keep in mind, the prefix Clone is automatically added to the Summary of a cloned issue. Your project admin can use Automation for Jira to remove the prefix in bulk. Learn more from our Community and see an example of the rule.
I've setup the following hierachy for one of our projects: 1 level: Initiative -> linked to Jira issue type INITIATIVE. 2 level: Epic -> linked to Jira issue type EPIC. 3 level: Stoy -> linked to Jira issue type STORY. 4 level: Sub-task -> linked to Jira issue type SUB-TASK. Step one: Download the desired tool from the marketplace. In this case, we're going to be using Microsoft Outlook for Jira as a guiding example. Step two: Install the add-on to your Outlook. Step three: Connect your Outlook to the add-on. Step four: Go to the add-on from the required email and create an issue, or even add the email to an oXmGQ.