Epics have Date ranges (start and end dates), but because epics can have child records — features — you can choose to have an epic's dates Calculate from features. If you select this (or if a workspace owner has set this as the Record dates default setting ), your epic's Start date will be the same as the earliest feature Start date and its
1 accepted. to the best of my knowledge it is impossible to share components and versions across projects (globally). But labels can be used across the groups. considering your company structure; seems like you should only create one project in your Jira. If you do so; you can share components , versions and epics.
condition: issue type is not epic. condition: epic link is not empty. action: lookup issues on JQL where "epic link" = { {triggerIssue.epic link}} branch: on epic parent. edit issue fields: setting the story points to { {lookupIssues.Story Points.sum}} Of note: this works for a company-managed (classic) project. Apr 13, 2020. It's possible. But not in Next gen. You need a board, an epic and a classic project. In a board, you would need to specify the epic. Let say if the epic is created in project A but will also be used in project B, in the board, you would need to include Epic from project A in the board filter. Basically, you would need a custom 1 accepted. This is how I figured it out - basically Branch rule / related issues > JQL > "Epic link" = { {issue.epic.key}}. This searches for other issues within the same epic (then putting whatever conditions you want after that). Welcome! I believe that in this case the problem is in the type of branch used. I created an epic that is too large. I want to split it into 2 and re-define requirements across two epics. In grooming, one story is estimated too large. I want to split it into two stories; Current Solution: Cloning - However, I lose track when using two tabs. I would do it away from the team and they have to wait on a future grooming to re GRrS3.