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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Github smart commits transition workflows when not using default branch

How do you get the smart commits to only transition workflows on the default branch? Currently when we push smart commits to a non-default branch is transitions the workflow. This seems like I must be missing something obvious.

1 answer

0 votes
Dario B Atlassian Team Nov 19, 2020

Hello @Wyatt Mufson ,

Welcome to the Atlassian Community!

As outlined in the Process issues with smart commits documentation page, in order to transition an issue using smart commits you need to enter something like below text in the commit message:

<ignored text> <ISSUE_KEY> <ignored text> #<transition_name> #comment <comment_string>

The above commit message will make the issue having ISSUE_KEY transition to transition_name.

So, I believe what is happening in your case instead is that you have a workflow trigger that is making your issues transition on some specific conditions (e.g. commit created). 

Can you kindly check if this is the case?

 

For further details:

 

Cheers,
Dario

When the commit message <ISSUE_KEY> #resolve is committed to any branch, it transitions the issue to resolved. What we need is for this to happen only if the commit being committed to the default branch (i.e. master). With the current behavior it closes the issue before a pull request is reviewed.

Dario B Atlassian Team Nov 20, 2020

Hi @Wyatt Mufson ,

I might be missing/misunderstanding something, but this seems to be the expected behavior: if in a commit message you explicitly tell to Jira to resolve an issue then Jira will transition that issue to resolved status.

Can you share a bit more details on what you are trying to achieve since there might be another way to get to the same results? 

 

Cheers,
Dario

We want Jira issues to close when the code that resolves it is merged into the default branch and not just any branch. Since this does not seem to be an out of the box feature of Jira we've decided to use a different product.

@Wyatt Mufson , 

Please notice nobody said it cannot be done in Jira, it was just mentioned that there is another/different way to do it.

Specifically: if you only want to close the issue when the code is merged into master, then you should either use a  workflow trigger  or an automation rule on the "pull-request merged" event.

For more details see also the below thread:

https://community.atlassian.com/t5/Jira-Software-questions/Transition-issue-when-pull-request-is-merged-on-a-specific/qaq-p/1028581

 

Cheers,
Dario

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

868 views 14 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you