Smart commits stopped working on couple branches

julius_bischoff
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 26, 2020

tl;dr:   

Jira Server <-> Bitbucket Cloud   via DVCS-Connector

Smart commits still working in branches Master and corresponding hotfix-branches. 
Smart commits stopped working in develop and feature-branches.

We don't know why.
Only clue could be a debug output, but we can't reproduce it e.g. make a commit with the same debug output.
Maybe the change occurred after we first tried creating a branch for an issue via jira (did not work as we thought) and merging it back to develop.

 Smart commits disabled for changeset: Changeset{repositoryId=1, node='3d1.....'}

 

Does anyone have an idea how to solve this?

 

Long Version:

(BitBucket Cloud and Jira Server 8.7)

So we moved from the Bitbucket internal Issue Tracker to a self-Hosted Jira-Server about 6 months ago. We started and created workflows and so on and made them work with smart commits. We solved some user/e-mail issues and status transtions stuff. It all worked like we wanted. Our couple developers could start commiting smarter, tracking time and so on. 

We have a master branch with the production version of our platform. With each major version bump we create a hotfix-branch which takes care of minor version bumps. On the other side we have the develop-branch with some feature-side-branches.

Only hotfix-branches and the develop-branch are allowed to merge into master.

Right now the smart commits in hotfix-branches are tracked. Those in develop branches are not tracked and therefore don't show up.

We tried that with a seperate issue and made debugging smart commits from various branches and users. Only those in master and hotfix branch would show up. 
We tried relink our bitbucket repository. (it seemed to scan through all commits) but it did not help.
We activated debugging logs and the dvcs and smartcommit plugin. 
(com.atlassian.jira.plugin.devstatus.smartcommits and com.atlassian.jira.plugins.dvcs)

Only one time we got an odd output:

2020-02-19 13:36:15,173+0100 DVCSConnector.EventService:thread-1 DEBUG username.anonym [c.a.j.p.devstatus.smartcommits.DefaultSmartCommitsEventBridge] Smart commits disabled for changeset: Changeset{repositoryId=1, node='3d1d.....'}

But we cannot reproduce this output somehow.

It might have something to do with a feature branch we tried...
When we just move to Jira, we tried the create a branch from within Jira. This created a branch with a ticket-id and title. We thought each commit would be tracked with out putting the ticket id (MFL-123) in the commit message. That was not the case...(should have read the docs), well the issue was set back and is worked on now, 5 months later. 
Well we merged that branch into a develop-side-branch and that into the develop-branch.

Maybe that messed things up?

Well we want all our commits to be tracked by Jira. Since we use Jira our ProjectHead doesn't monitor the bitbucket-commits-list and see progress. right now she only see Issues not progressing even though plenty commits and work is being done.

Hopefully anyone has an idea.

0 answers

Suggest an answer

Log in or Sign up to answer