Not sure why but we have intermittent failures of the post-commit hook that creates the bi-directional link between the Stash commit and the Jira issue. The commit msg clearly states the correct issue key but the link is not established. What is the quickest, preferabably end-user-executable, way to retro-actively establish the link?
Less preferable but also helpful would be an admin-level, Git-savvy approach.
There may be several reasons why the link doesn't show up. To figure out what's going on, could you tell me:
If the links are missing on both sides, it's likely that there's an issue with the indexing of commits on the Stash side. If you are seeing the links in Stash but not in JIRA, it could be a permissions issue where the JIRA user doesn't have read access. Alternatively, if the commit only exists in a forked repository, it won't show up on the JIRA issue. See https://jira.atlassian.com/browse/STASH-3403and https://jira.atlassian.com/browse/STASH-4541. We plan to improve the indexing of forks in a future release, but currently forks are only partially indexed for performance reasons.
That sounds like an issue with either the changeset indexing or the git hook on the Stash server. Can you open a Stash support request on https://support.atlassian.comand reference this answers thread? Please upload a support zip (Administration > Support tools) so we can have a look at your logs to find the cause.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot