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
4,369,005
Community Members
 
Community Events
168
Community Groups

Conflict resolution workflow

Bitbucket has a very nice feature to detect conflicts prior to issuing a merge. Crucible appears to not have this same feature or if it does, I'm not certain what the path to activating it is. I expected the "auto update" feature in crucible to just detect this and subsequently show me something similar to what I see in Bitbucket but alas - that did not occur.

I made two branches from a common branch, made conflicting changes to each branch and pushed both out, merging one of the branches down to the common root branch. Then I made a crucible branch review from the non-merged branch to the common root but it has not "auto updated" yet.

Is this a known issue? Can I solve this problem? Is my question clear (I hope)

1 answer

any chance a bump comment will get this question noticed? :) thanks (if it works)

@twx_clint : Super old question... did you ever get an answer to this, even if outside of Community!?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events