Just as Pete was saying, a remove & re-add of the DVCS connector cleared up our issue. Tried a bunch of different fixes. This was the only thing that worked.

@Bill Goetz yes believe so - Remove and re-add to tickets.

The tickets themselves don't get transitioned or anything during the remove/re-add IIRC. Just a case of the attribute not being available during the change period.

@Pete Stanley, do the commits essentially get removed from the Jira tickets and re-added after re-sync? Did you see tickets become updated when this occurred? I know you say "little risk", but just trying to do a CYA from my standpoint. 

@Bill Goetz, it really depends on how many repositories and historical commits you have to sync. For our well established GitHub account (About 10 years old with ~100 repos) took about 24 hours to sync. You might want to do it over a weekend or plan an outage window with your dev teams.

@Pete Stanley,  how long did it take for the entire "remove and re-add" process to occur? We are considering your solution, but hoping to have some insight into the timeframe. We have over 700 repos.

For those still struggling with this, one way to deal with it is to remove the integration and setup from scratch.

You could just create a new authentication token rather than completely setup the integration again but I had some other technical debt to deal with...

Either way, there's little risk in setting up from scratch as Jira will sync all historical commits from GitHub once reconfigured:

1. Log into your GitHub account (Works for 'Team' or 'Enterprise' accounts).
2. Navigate to Account Settings > Applications > Authorized OAuth Apps > Jira DVCS
3. Delete any existing DVCS connector titled "Jira DVCS" if it already exists.
4. Navigate to Account Settings > Developer Settings > OAuth Apps > Create new OAuth App
5. Set the following:
   1. Application name: JIRA DVCS 
   2. Homepage URL: https://<YOURJIRASERVER>.com
   3. Authorization Callback URL:  https://<YOURJIRASERVER>.com
   4. Save the new application.
6. Generate a new Client Secret - Note this down somewhere safe (e.g. a password vault). It will only be displayed this once.
7. Save the Client ID (key) along with your Client Secret somewhere safe.
8. Navigate to Jira > Settings > Applications > DVCS accounts.
9. Disable/remove any existing instance configuration for your GitHub account. (This may take some time due the size.)
10. Refresh the page once complete to verify the GitHub account has been removed 100%.
11. Choose "Link Bitbucket Cloud or GitHub Account".
12. Complete the following:
    1. Host: Github
    2. Team or User Account: <COMPANYNAME>
    3. Client ID: Enter Client ID previously created.
    4. Client Secret: Enter Client Secret previously created.
    5. Auto Link New Repositories: Yes (Checked)
    6. Enable Smart Commits: Yes (Checked)
13. Note, the initial sync may take hours/days and can take several attempts due to GitHub rate limiting.

@Marcel Haase

We are creating an access token earlier this year and when trying to create a fresh token it has the same length and the same format

Regards

Hello,

It is another "error" . You have to go into github and reset your Auth token (secret token) of the dvs Auth app on github. 

Github changed the format of the secret key. (i.e. length) 

Please follow the steps in the "error"-mail on github and after resetting the token, you shouldn't receive these kind of "error" / notice.

Best regards

We are running Jira Software Version (Data Center) 8.14.1 and still receiving emails from GitHub stating we are using an API with an outdated format. What do we need to do to stop these notifications?

Hi all,

We are running Jira Software Version (Data Center) 8.14.1 and still receiving emails from GitHub stating we are using an API with an outdated format. What do we need to do to stop these notifications?

Please advise

Thanks

James