Why aren't workflow statuses updated with triggers?

[Nicki Hinkell]

Our JIRA OnDemand instance is configured to display development updates from GitHub. This works (with some delay) and we've been using it succesfully for at least six months.

I recently discovered Triggers: https://confluence.atlassian.com/display/JIRA/Advanced+workflow+configuration

I updated two of our workflow status transitions such that tickets should transition to In Progress on branch creation and get Resolved when the branch is merged. As far as I can tell, everything is correctly configured (per the directions on Confluence).

However, nothing happens when my teammates branch or merge. Interestingly, the tickets still update with GitHub status(es). I have re-synced our repos and everything--no luck. The tickets correctly indicate that changes have been MERGED but workflow transitions never happen (we waited about a day and a half before concluding that it wasn't working).

I haven't been able to find any documentation on this. :/

[ZehuaA]

Hi Nicki,

From what you described, you might be affected by https://jira.atlassian.com/browse/DCON-448, especially if you see error msg "Error during sync. See server logs" on the DVCS Accounts page. But this affects only pull requests, which would affect the "branch is merged" trigger. It should not affect the branch created trigger.

If you are only seeing delays of up to one hour in the triggers, then it could be due to https://jira.atlassian.com/browse/DCON-453. You could try the workaround.

When you say "re-synced", do you mean clicking on the sync icon on the DVCS Accounts page for the corresponding repository? If you do a full sync, which is done by holding the Shift key and clicking on the sync icon, then any events generated will not cause the trigger to fire. So be sure to just do a normal sync without using the Shift key.

A tip on troubleshooting is to look at the History tab of the issue. Sometimes, multiple triggers might be fired at the same time and cause the issue to go back and forth between two statuses, especially if you use global transitions in the workflow.

Cheers,

Zehua

[Nicki Hinkell]

1. I have seen "Error during sync" although not consistently and only for one repository. I will see if today's (?) update resolves this
2. The delays are permanent... the triggers aren't ever firing
3. I meant clicking on the sync icon (without holding Shift)
4. History is not updating--there is no indication that tickets have been moved back-and-forth between statuses

Thanks!

Nicki

[Nicki Hinkell]

FYI - The update did not resolve this. Triggers are still not firing.

[ZehuaA]

Hi Nicki,

Could you raise a support ticket at https://support.atlassian.com, as what Tim suggested above?

Cheers,

Zehua

[Nicki Hinkell]

JST-108371

[TimP]

Hmmm.. that is interesting. I've been poring through the code and I can't immediately see why it would be excluding updates to branches other than master. I'll ping the dev team responsible for the new workflow triggers to see if they can shed any light on the issue.

If this is critical though, I'd recommend raising an issue at https://support.atlassian.com as they'll respond much quicker.

[Nicki Hinkell]

So interestingly enough, while I was procrastinating on looking into this... one item unexpectedly transitioned.

It appears that the triggers only fire in response to activity against master, where most of our work is happening in the develop branch. Branches created off, commits against, and merges back into develop are displayed under Development modules but do not trigger workflow changes.

Merges against master do trigger workflow changes. I'm now trying to determine whether this is configurable.

[TimP]

Hi Nicki,

From your description it sounds like you have everything set up correctly. I'd double-check that the workflow you've configured is associated with the correct project and then raise a ticket at https://support.atlassian.comif you're still seeing problems.

Please reply here letting us know what the problem turns out to be, so other users might benefit from the fix :)

cheers,

Tim