In general, you can locate issues which have an Epic Link applied (as long as this is a Classic Project): Action: Issue Updated. Condition: Advanced Compare Condition - { {issue.Epic Link}} (first value) does not equal (condition) - then leave "second value" as Empty. ^ Then, utilise: Branches to locate the related/linked issues. You can't move standard issue (bug) and other standard issue type task. You want to move this , you can convert issue type to sub-task using convert to sub-task option. With this you can mention task ID as parent for the sub-task. Thank you. Yes, this I know, I just guess if it possible to move the issue as a Bug not converting it into a sub-task. You can also link to other Jira applications like Jira Software or Confluence. For example, you might want to link an incident to Jira Software when a second or third line support member needs to work on a fix. To link an incident record to a task in another project: View the incident record. Select the more menu (). Select Link. Add an epic from the Roadmap: With the Roadmap open, select “More” (…) in the top right and then “Board settings”. From the Roadmap tab, then click to enable Epics for your project. On the left sidebar, then click Roadmap and select “+ Create epic” (if the Roadmap isn’t populated, you just need to type to add your first Epic) In 1 accepted. It sounds like you need to take this step so that your Portfolio Epic is available in the Parent Link field: Select> Products. In the menu on the left, select Advanced Roadmaps hierarchy configuration. Select or remove hierarchy levels you want to include in your plans. Select Save changes. 1 accepted. In a project roadmap you can only see issues from that project. If you're on the Premium plan then you get access to Advanced Roadmaps - a different product (formerly Portfolio but now integrated into Jira Premium) which will allow you to arrange multiple projects/boards/filters in one view. It's pretty good, but at an added cost. If so, go into issues > issue type hierarchy. That said, this isn’t great practice in Jira. Think of Epics in Jira as Features in SAFe, then Initiatives in Jira as Epics in Safe. You can opt into the epic renaming beta, or just get your people used to the (truly aggravating) terminology mismatch. I actually did a whole piece about this today I have defined a Jira Project with a number of Initiatives. Under each Initiative, there is a number of Epics that originate from different Jira Projects. Under each Epic, there are tasks that come from different Jira Projects. I am struggling to find a query that will dynamically list all of the Epics and Tasks that are added to the Initiatives. Epic -> 3. In Progress Story -> 2. In Progress Sub-task -> 1. In Progress When the Sub-task is moved to 'In Progress' I would like the Story to then transition to 'In Progress' (easy, already done) AND also update the Epic into 'In Progress'. Can I create a rule to do this using Jira Automat Under Jira GreenHopper (v6.0.6) there is a new feature. Jira > Agile > board > Plan, drag and drop the Story Issue onto the Epic. Using an old view, navigate to the story page. There should be a Epic Link field. Clicking on it and changing the value of it, should move story to the appropriate Epic. ujYXqN7.