It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
We are using Mercurial as our source repository, and each build shows changes from other branches as "M", meaning that they were supposedly merged into the current branch, but they weren't. Changes that were never merged into the current branch are still showing up as changes made to the current branch.
Also, in some cases, commits from other branches will even kick off builds for the current branch.
How can we get around this issue?
Do you mean you're seeing changes from unrelated branches showing up in your branch commit list?
Please submit a support ticket via support.atlassian.com. Make sure you mention your Mercurial version and OS in the ticket.
Yes, unrelated branches, other branches, any way you want to put it. I'll create a support ticket for this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.