Ok, it's time to re-surface that handy structure diagram because it’s time to start moving left-to-right. A Milestone is a collection of Epics that together define the work to achieve a specific Milestone. Milestones can be based on time, OKRs, projects or other goals. At Shortcut we currently use t ime-based milestones, with a milestone per If the trigger issue is Epic I need to iterate through all issues in epic and copy custom field cf [10112] "Project team" to every issue in epic. I know you can use. def query = jqlQueryParser.parseQuery ("\"Epic Link\" in ($ {issue.key})") def results = searchProvider.search (query, user, PagerFilter.getUnlimitedFilter()) And then iterate with. The "Epic" is still an container, to structure work on the team level. Using SAFe, we created a new level above the "User Story" Level for issues of the type "Feature". A Feature can be broken down in "User Stories". To aggregate all Story Points of an "User Story" issues to a "Feature" issue (done in one PI) we have to use the "Parent Link". Parent Link field is created automatically, please follow the below. Go to your Project Settings > Screens. Under the Epic issue type, click to add a field to the screen. Depending on if you've separated your Issue type screen scheme. Search for the Parent Link field and add it. Navigate to the Issue view and search for the Initiative under the Yes, it is possible to show Epics from Project A that are associated with Stories in Project B on Project B's board using JQL filters in Jira. You can use the following JQL query: project = B AND "Epic Link" in (project = A) This query will filter out all the Epics from Project A that are not linked to any issues in Project B. Story points are a core concept in agile planning, and can only be used by those planning for scrum teams. It can be used for both issue estimation and tracking the progress of work on a board. By default, story points can only be assigned to story or epic-type issues, and not subtasks such as bugs. This can be changed by those with Jira Answer accepted. "Epic Link" in ('') expects issue keys, e.g. "Epic Link" in ('KEY-2', 'KEY-5') Filters do not return issue keys so this will never work in JQL. You would need more "sophisticated" functions such as 'issueFunction in linkedIssuesOf ('project= EPICPROJ', 'is Epic of')'. Such functions are specifically tailored to find you linked Epic Statistics on the Story Map. In Jira Server and Jira Data Center, a progress bar will show at the top of epic cards on Scrum boards. Epic statistics shown as the blue progress line under the Epic colour . This progress bar is pulled in from the Jira backlog and hovering over the blue line on the Story Map reveals the epic statistics. HFnz.

jira when to use epic