How to resolve an issue in a different bitbucket repository with a commit message?

[jakard]

Hello.

I want to manage sources and issues with bitbucket.
But I don't want that my testers see my sources.

So I created two repositories, one is for sources and the other is for issues.

I refered to github help. 

https://help.github.com/en/articles/creating-an-issues-only-repository

I thought this way could be resolved my problem.

But I couldn't resolve an issue in a different repository(issue repository) with a commit message.

Github support this problem like this.
https://help.github.com/en/articles/closing-issues-using-keywords

How can I resolve this issue?

[Ana Retamal]

Hi! 

You're posting your question in an Atlassian forum (Bitbucket) but you're referring to Github documentation. Could you clarify which product are you using?

If you're using Bitbucket Cloud, you can solve this by making the issue tracker public (so everyone can submit issues) and keeping the code private, all this in the same repository. If you don't want your issue tracker to be public then you'll need to separate repositories, but note that commit messages will not work across separate repos, they will only apply to the same repository where they're being committed.

If you're using Github, I'd recommend you to visit the Github forum. 

Hope this is clear, please let us know if you have any questions.

Best regards,

Ana

[jakard]

Hi!

Thank you for your reply.

I'm sorry about that my question was not clarified.
Actually, I'm not familiar with English.
I'm using bitbucket cloud. And what I hope is the second case you answered.
In order to prevent test users from accessing sources I seperated private repositories for sources and issues.
And I refered the github link to know how to resolve or close issues with commit message like doing in github.
Thank you Ana.

[Ana Retamal]

Hi again, don't worry, I'll try to help you :) 

I understand that you'd like to have both your issue tracker and source code private. As you already did, you'll need separate repositories for each of them. 

However, note that in Bitbucket Cloud is not possible to use references across different repositories, they'll only be applied to the same repository where they're being committed.

There's a Feature request for that in our issue tracker, however it was closed as 'Won't fix'. My suggestion would be to comment on there so the developers know that this feature is still wanted, or alternatively you can create a new feature request. You can find it at Issue #8085.

Let us know if you have any other questions. Hope that helps!

Ana

[jakard]

Thank you Ana.