JIRA Stash Workflow Triggers

[RobertH]

Screen Shot 2014-12-02 at 3.14.24 PM.png

I'm trying to use workflow triggers in stash/jira.  It's not working at this time.  It looks like JIRA is querying the following URL:  https://jira.whatever.com/rest/dev-status/1.0/trigger/diagnostics/pullrequests?_=1417471751091

This yields a JSON page that says the following:

{"appLinkDiagnosticResults":[{"name":"Stash","type":"Stash","icon":"https://jira.whatever.com/s/en_USu99ehe/6336/73/4.2.4/_/download/resources/com.atlassian.applinks.applinks-plugin:applinks-images/images/types/16stash.png","supportedVersion":true,"accessible":true,"inboundStatus":"NOT_REACHABLE","outboundStatus":"WORKING","local2LOConfigured":"OK","remote2LOConfigured":"OK","working":false}],"dvcsDiagnosticResult":{"pluginConnected":false,"dvcsAccountDiagnosticResults":[]}}

It looks like this is where it's saying that it can't create the triggers.  I'm not seeing anything relevant in the error logs.  Also, both application links are in place.  I've used the SSLPoke classes, and both can connect on the appropriate ports.  The application links are set up properly.  No complaints between the systems.  

Is there some other way to troubleshoot this?  I set com.atlassian.applinks to INFO in the logging.  Nothing.  I've checked the stash server's log.  Nothing.  

Any further troubleshooting tips would be fantastic.  

[ThiagoBomfim]

Hi Robert,

At the bottom of the page below:

• Configuring workflow triggers

Please review the section "2. Check for common problems" under "I cannot add a trigger to a transition". Can you make sure your AppLinks are configured (on both sides - Stash and JIRA) as per our requirements?

• JIRA + Stash/FishEye/Crucible: You need to configure a two-way application link using Oauth with 2LO and 3LO.

Best regards,
Thiago Bomfim
Atlassian Support

[RobertH]

Both are set to use 2LO. Documentation says these applications support 3LO by default. If there's somewhere else to turn that one, let me know. I'm thinking it may be related to this bug: https://jira.atlassian.com/browse/JRA-40968

[ThiagoBomfim]

Hi Robert, Thanks for looking into this. If that's the case, did you try applying the workarounds suggested in the JAC you linked?