Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Two Jira instances - Smart commits problem


When I make smart commit on Bitbucket repository, the commit are handled great. I mainly use it for work log and it works fine. But from my second Jira instance I always receive mail that "There was an error processing your smart commit".

And further there is info:

"Jira could not log time against the issue MYIS-2

We encountered the following error:

The MYIS-2 issue doesn't seem to exist."


But actually there is not such issue in that Jira instance, so I don't want to log anything from my smart commit. So I don't need such error. How to turn it off?

The issue I want to log my smart commits is on another Jira instance and it works fine.

For any help great thanks in advance.

Best Regards

3 answers

0 votes
Daniel Ebers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 12, 2023

Hi @Wojtek Pilwinski

it looks this is best described by the following bug which is still in status "Gathering Impact", though:

While this is for a on-premise setup it looks the initial issue is the same:

For environments where multiple JIRA instances are connected to Bitbucket with the same user bases this will result in unnecessary failure emails. These confuse users and drive support calls.

You could watch the linked bug and vote for it, signalizing it is of importance to you.


Hello hello,

I am still wainting for help 🙃

You are all beautiful people and I love you, but please help me with that stupid issue.

Best regards.

Really no one of you met similar problem?

Please help me.

It is annoying when I receive many not relevant e-mail notifications about error.

Suggest an answer

Log in or Sign up to answer