My company has a subscription to Jira cloud at https://smashingboxes.atlassian.net As part of that setup, we have a Github integration, which is supposed to pick up smart commit messages, and display commits, branches, and pull requests, as well as trigger transitions on our boards. For some projects/git repos, this is working great. However, recently a few of them have stopped working.
I've tried going to Admin > Applications > DVCS accounts > ... > Refresh repositories, but the repositories I'm interested in are not showing up in the list, or the autosuggest dropdown.
That is odd. It's the same project and the commits are capitalized so that rules out JSWCLOUD-15764 which deals with project keys that are not capital.
At this point I have created a ticket with our Cloud team and they will reach out to you shortly to help you resolve this as they can see the logs on the backend. Once this does get resolved please let the Community know what the root cause and resolution were in case someone else runs into this same issue.
In the meantime please also take a look at Commits missing in Commit Tab
Run the following command
Mercurial:run hg log
Check if some commits related to the issue have the correct user and email adress.
Some Commits do not have the correct email address linked, this causes JIRA to fail looking up the proper author on Bitbucket and thus does not display the commit.
A commit should look like the following:
commit aa1a1b1e11e1ca2baad8aa2aaad9aaaaedbdc07a Author: John Doe <firstname.lastname@example.org> Date: Tue Feb 19 16:20:28 2013 +0100
All Contributors will need to properly set their .hgrc or .gitconfig, for all future issues the commits will show properly.
If that helps take a look at the To fix the commits for old issues section of the Commits missing in Commit Tab to fix the old issues.
In addition, please let the Support Engineer that contacts you via the ticket that the issue is resolved or let me know and I can pass that info along.
I was contacted by Jira cloud support, and we determined the root cause. The "authorizing user" that was initially used to add the connection between Jira and Github was removed from our github organization, and thus could not access the repos anymore. I'm still working on the exact resolution, but most likely it will involve creating a new user in Github explicitly for this purpose, add it to our organization, and then use that user to make the connection to Jira.
Hey Atlassian community, I am a PM on the Bitbucket Cloud team and I am excited to share that we just released an improvement to the Jira Software and Bitbucket Cloud integration. With the newly im...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs