Sync epics with their issues and configure parent/child relationships between them

[mattreid]

Syncing upstream issues to Jira for greater visibility and goal tracking is helpful, but to make them even more visible, and automate as much of the unified backlog connection process as possible from the metadata we have available in GH will provide the most value, and help teams more easily maintain a unified backlog, and not just a flat backlog of issues synced out of GH.

There should be a supported pathway from GH issue types, metadata, and relationships, to having those synced issues have expected parent/child relationships to create chunks of a unified backlog. If synced stories include their epic, then the development team only has to create a feature and connect that to an outcome in Jira for a unified backlog and full hierarchy. Without sync2jira being able to understand epics and create parent / child connections, a team would then have to create features and epics in Jira, connect those, and then find the right synced stories to connect to epics, which is a lot more overhead.

We should strive to minimize the day-to-day burden on teams and make it as easy as we can to establish and maintain their unified backlogs in the future, if we want Jira visibility to be valuable to stakeholders.