b4978340ff6b,

As I updated 3 years ago, any branch you directly update is sent to Jira, regardless of whether it is in a fork. So if you use a fork-based workflow and you push all your work to your fork, those branches will appear in Jira. At this time we're not working on any further changes in this area, and it's not on my personal agenda to work on in my spare time either. Is there something specific you're still looking for? I'm not sure a day will ever come where all branches in all forks are listed in Jira. Personally, I don't see any significant value in listing every repository in a hierarchy simply because the branch is present. Especially for developers who use fork syncing, you end up with many branches present in your fork that you don't actually care about. Any branch you actually push to will appear in Jira, though.

Here's a screenshot from this issue's dev panel:

That test branch is in my personal fork of the Bitbucket Server repository. Since I pushed directly to it, it was indexed in Jira.

Best regards,
Bryan Turner
Atlassian Bitbucket

Is there any update regards?

I.e. can I today able to see in Jira issue branches from forked repo?

If the answer is not, then when it's suppose to be solved?

By the way, I know that branches from forked repo in Github and Bitbucket is working.

i_boyko,

Unfortunately, no. The new behavior is the only behavior. Trying to make it configurable per repository would add a fair amount of complexity (for the code but also, more importantly, for administrators, who would need to configure it all, and for users, who would need to understand why their branches appear in JIRA for some repositories but not all repositories without being able to go "look" at the settings).

Do you have a specific use case you're targeting?

don.draper1814139281,

I hope it's a useful improvement for many! My apologies for it taking so long to ship.

Best regards,
Bryan Turner
Atlassian Bitbucket