Stash branches and commits in user profile forks not visible in Jira.

[Doug Hanks]

We are using a Fork workflow in Stash and have integrated our Stash and Jira instances.

When a branch is created in the developer's fork in their profile, the branch does not show in the Jira development panel for the issue. The branch does have the issue key in the name.

When commits are made and pushed to this branch, the commits also do not show up in the development panel. The commit messages do contain the issue key.

When a pull request is made from this fork back to the original repository in a project, the branch and commits appear in the development panel.

Does the Jira/Stash integration ignore repositories in a User profile, or might I have soemthing set up incorrectly?

[Michael Heemskerk · Accepted solution]

Hi Doug,

Unfortunately, you've hit a known limitation. For performance reasons, forks are only partially indexed by Stash. Branches and commits that exist only in forks won't show up in JIRA, but the links to the JIRA issue will be displayed in Stash. When you create a pull request, Stash creates a (hidden) ref for the pull request and fetches the source branch into the target repository. At this time, the commits become visible in the main repository, are fully indexed and the commit links will show up in JIRA.

We plan to improve the indexing of forks in future releases. Please watch (and vote for) https://jira.atlassian.com/browse/STASH-4541if you want to be notified of any updates on the issue.

Cheers,

Michael

[Doug Hanks]

Thanks Michael.

I just noticed that if I create the pull request inside the fork, the links do show up in Jira. So something in the pull request process triggers even the forks to be indexed. I'll watch the issue you referenced.