New Github Repo not recognized by JIRA Github App

Craig Wells August 15, 2023

So we integrated GitHub Cloud into JIRA Cloud using the Github for JIRA app by Atlassian.

We were able to get 1 repo connected and everything is working as expected. Given that we wanted to add an additional repo in Github to JIRA. To do that I did the following:

  • Went to the Configuration page for 'GitHub for JIRA app'
  • Clicked on the pencil icon next to the 'Only selected repos (1)' text
  • Logged into GitHub and selected the second repo we wanted to add to the list to be synced with JIRA.
  • Saved that change
  • Went back to the JIRA app configuration page and noted it still said 1 repo was selected instead of 2.
  • I refreshed the page and there was no change
  • I waited an hour and refreshed and there was no change
  • I waited for an additional 2 hours and still no change

I'm not sure what is going on and why it's not picking up the new repo. Is there a delay on when JIRA will pick up the change in the config in GitHub? If so, how long is it?

Does anyone else know why this isn't working?

2 answers

1 accepted

0 votes
Answer accepted
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 16, 2023

Hi @Craig Wells 

In the configuration at the end of line of your organization config you could click the 3 dots and check "continue backfill". This will start sync of data from github to jira (I just did that in my test environment. It does update the line/number of repositories, can´t exactly say what it does with rest of data/commits/PRs that my have been done in the past).

Furthermore:
Did you try to use the newly added repository in a project/issue? I´ve experienced this behaviour in the past that newly added repositories were not shown in Jira (especially in the "code" area of a project) unless they were linked to any issue. So did you try to make a change in the repository (could only be changing the readme) and mention an issue key in the commit message?

Best
Stefan

Craig Wells August 16, 2023

Thanks, Stefan. I tried the backfill option as suggested, but that didn't change the number of repos in the JIRA Configuration page.

However, I did ask one of our engineers to try and use the new repo in JIRA and he reported that it was working as expected. It seems that we're dealing with the issue you mentioned in the second part of your message.

 

Craig

Like # people like this
Stefan Salzl
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 16, 2023

Great to know it works. Thanks for the feedback 🙌🏼

0 votes
Rafa May 3, 2024

I had the same issue and the way I solved it was to unlink jira/github and link again, and then it saw the newly added repositories.

(However, this does trigger a re-index of all github commits...)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events