nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DVCS connector with Git and workflow transitions

motherg

Hi all,

We've been using the DVCS connector with Git and GitHub at work for a while now, it allows us to tie our commits to the stories just fine but the feature we really want is the ability to transition the stories through the workflow. We use a custom workflow - no preconditions on the steps (there are some post conditions).

That categorically doesn't work, regardless of the format we go with. I've tried all the recommendations in the thread here. You can see I've commented there too but I'm no longer getting responses.

Any suggestions?

Accepted answers

All comments

StevenA

Hi,

It is because your workflow transition does not have preconditions on the steps. Just add a new transition condition with the choosen option as:Code Committed Condition

Best Regards,

Steven

motherg

Aha! Thanks I'll try on Monday - is that mentioned anywhere in the documentation? I didn't see it and I think I've read it cover to cover.

StevenA

Thanks, I will try to get this on document updates

motherg

Hi Steven,

Just checked it out - this doesn't seem to be a good setup as it means you can only move things through the workflow via Git commits?

It's one extreme or the other, why would anyone want to be restricted like that? I struggling to see a use case where that is a valid argument.

I'd imagine most users would want the added ability to transition an issue through the workflow via git commits but not be exclusively tied to it?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

git

github

dvcs