Code Committed workflow condition with Stash

It seems like when I commit code in Stash with an issue ID in the message, even though jira will show that commit in the "source" tab of the issue, it will not satisfy my workflow condition of "code must be comitted" (from the fisheye/stash plugin). Has anyone gotten this to work, or experienced this same issue? I have both fisheye and stash linked to my instance of JIRA.

1 answer

1 accepted

1 vote
Accepted answer

Hi John,

The workflow conditions bundled in the JIRA FishEye/Stash Plugin currently only support querying for code changes in FishEye. You could work around this limitation by making FishEye index your Stash repositories as well, but you would end up with duplicate commits showing up in JIRA (one from Stash and one from FishEye for each commit).

If this functionality is important to you, the best course of action is to raise a feature request for the Stash to support the FishEye workflow conditions in the Stash project at https://jira.atlassian.com.

cheers,

Tim

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Jira

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,084 views 0 8
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you