GitHub Integration Settings Per Project

[Ashley Graham]

We currently have a GitHub enterprise account and an Atlassian Cloud enterprise account. Each of our software development teams has slight variations in their developer tools usage. And as a result, we're hitting an issue (we believe) due to the 1:1 integration between GitHub and Jira Software Management in the Atlassian apps.

One team, for example, uses GitHub and GitHub Actions for all of their builds/deployments. Another uses parts of GitHub, Octopus, and TeamCity. Is there any way to remove (at the project development tools level) the GitHub Actions piece on certain projects? GitHub Actions are showing on the Builds tab for this team, but they only want to associate TeamCity to the builds tab and Octopus to the deployments tab.

We tried examining the settings within the GitHub application in Jira Administration and in looking at the settings in GitHub enterprise. Neither seemed to allow the granularity we need. Has anyone else run into this use case?

[Mathieu Lepoutre _Exalate_]

Hello @Ashley Graham 

I work for Exalate.

When importing issues via CSV from Jira Cloud to Jira Data Center, ensure that the Epic link field is correctly mapped. The connection between Epics and tasks can be tricky, especially if the field configurations between Cloud and Data Center differ.

If manual mapping proves difficult, tools like Exalate can help with syncing issue links (including Epics) between Jira Cloud and Jira Data Center more reliably, ensuring proper connections between tasks and epics during the migration.

Thank you.

Kind regards,

Mathieu Lepoutre