If so, there is an Epics pane on the board Backlog screens and those show how many issues are in the Epics. You could also create a Save Filter that retrieves all the child issues, then use the Pie Chart gadget on a Dashboard to show the information based on using the Epic Link for the Statistic. That will show the counts per Epic, as each 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. Enable estimation for your team-managed project. If you’re not already there, navigate to your team-managed software project. Go to Project Settings > Features. Enable the Estimation feature. Once Estimation is enabled, you can select whether to use Story points or Time. When first enabled, the Story point or Original estimate fields are Configure progress % calculation on either "remaining estimate" or "original estimates". Epic Tree directly on Issue Screen. Display and manage Epics/Issues of your project. Real time edit option for Issue summary, status, time estimates, story points and assignee on the tree on the Epic Hierarchy. Rolled up percentage completion and at issue The backlog uses the same filter as the board linked to it. As long as your issue is found using the filter, it will appear on your backlog. So if your issue is not on the backlog, you might want to look at your board's filter and may need to edit this. The issue will still remain in Issues, as this is just the list of all issues in your project. Reply. 0 votes. Derico Zymn Oct 10, 2020. There is no much critical task , simple you have to select the all over Jira Tickets on your wishes format wither CSV, XLS etc then click to the Export button then you are good to download. Reply. 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. Epics - An epic is typically a very large user story, that is expected to take multiple sprints to complete. An epic is broken down into multiple stories, and is represented as an issue type in Jira. Stories - A story is a small body of work that represents a product requirement. Multiple stories can be used to make an epic. q05x7t.