How to properly set up Jira Cloud + GitHub + CI/CD pipeline integration in a Company‑Managed project

[Murali Ganesh Chitrothu]

Hi Community,

I need some help understanding the correct and recommended setup for integrating Jira Cloud → GitHub → CI/CD pipelines in a Company‑Managed Project.

My situation:

• I have Space Admin access (not Jira Org Admin).
• I am working on a Jira Cloud, Company‑Managed project.
• I have multiple GitHub repositories that I want to link with this Jira Project.
• My goal is to:
  1. See branches, commits, and PRs inside Jira issues
  2. Trigger CI/CD pipelines (GitHub Actions)
  3. Send build & deployment information back to Jira
  4. Use Jira’s Deployments + Code view effectively
  5. Automate transitions on deployment success/failure

What I have checked so far:

• I reviewed Atlassian documentation on integrating GitHub Cloud with Jira Cloud.
  (Ref: Atlassian Support: Integrate Jira with GitHub) [support.at...assian.com]
• I also checked guides about sending CI/CD build and deployment info into Jira.
  (Ref: GitHub Marketplace – Jira Development Integration action) [github.com]
• And CI/CD-to-Jira automation using Jira APIs.
  (Ref: “Integrating with Jira – GitHub Actions CI/CD” guide) [kindatechnical.com]

But I am still not sure about the correct sequence and permissions required.

---

My main questions:

1. As a Space Admin (not full Org Admin), can I fully configure GitHub integration?
   What permissions are required to connect multiple GitHub repositories to the project?

2. What is the correct setup workflow for:

   • Connecting GitHub → Jira
   • Ensuring commits/branches/PRs appear in Jira issues
   • Ensuring GitHub Actions sends Build & Deployment info back to Jira
   • Showing deployments in Jira’s Deployment view
     (Ref: Integrate your deployments with Jira) [support.at...assian.com]

3. For GitHub Actions:

   • Do I need to use the “GitHub for Jira” app only?
   • Or do I also need the “Jira Development Integration” GitHub Action?
     (Ref: GitHub Marketplace Action) [github.com]

4. Does each GitHub repository need to be connected manually, or can all repos within an organization be linked at once?

5. For CI/CD deployment tracking:
   What are the recommended best practices to ensure Jira shows:

   • Build
   • Deployment
   • Environment
   • Release status
     under the Development / Deployment panels?

6. Is any additional configuration required on Jira side, such as:

   • Deployment environments
   • Permissions
   • Automation rules

---

What I want to achieve ultimately:

• A complete DevOps flow where:
  Commit → PR → Merge → Build → Deploy → Jira Update → Release Dashboard
  works end-to-end with GitHub + Jira Cloud.

---

Any guidance, examples, best practices, or detailed steps would be hugely appreciated.
Thanks in advance!

[Matteo Vecchiato]

Hi @Murali Ganesh Chitrothu ,

Welcome to Atlassian community and thank you for your post.

I reply to some of your question:

1. As a Space Admin (not full Org Admin), can I fully configure GitHub integration?
   What permissions are required to connect multiple GitHub repositories to the project?

No, to fully connect it is required (see here ):

• Site administrator permission for your Jira site

• Owner permission for a GitHub organization

  • To check this, go to your GitHub organization settings and look for your permission level next to the organization name.

What is the correct setup workflow for:

Please follow this tutorial 

Does each GitHub repository need to be connected manually,

There are two options in the connector config section, connect all repos (and indirectly all the repos created after) or connect only selected repos (new repos created after won't be connected)

Hope it helps