How does JIRA process a submission?

[Elijah]

I am trying to find a data flow map that outlines how exactly a submission works through JIRA and I'm not familiar with any of the intricacies of JIRA.

The project I'm on has JIRA based on some event handlers / listeners push its data to a secondary database. What this means is that a submission to JIRA stores the record in JIRA but also pushes the complete incident to another database. This apparently has not been working for the past 6 months and I'm not clear on how it gets triggered in the first place. Can anyone point me to some tutorial as to how this may have been done or is suppose to be done. There is no transfer of knowledge on this project. All previous developers have left. I stand here alone guessing on just about every issue I have to deal with. Truly frustrated and ready to walk out the door.

So if anyone has any suggestions on where I can learn about this in an hour or so would be greatly appreciated.

[Nic Brough -Adaptavist-]

There are loads of ways this could be happening, but the three most likely candidates inside JIRA are

• Workflow post-functions that push data out to the other system
• A "listener" that pushes data out
• Webhooks in the workflow (See https://confluence.atlassian.com/display/JIRA/Managing+Webhooks )

All of these need admin rights to get at really.  I'd take a quick look on the system list of listeners to see if there are any possible candidates, but if there are none that look like they might be doing it, you need to descend into workflows and look for web hooks and post-functions too.  (Check out https://confluence.atlassian.com/display/JIRA/Configuring+Workflow for help with finding your way around them)

Although, for a listener and the post-function, it is almost certainly being done with an addon that allows you to add arbitrary code, or one written deliberately to do the work.  In both cases, have a look at "manage addons", narrow the list down to "user installed addons" and look for potential culprits in there.  Addons with your organisations name in it, or no description at all may have been written locally, but also check for "script runner"

I'm afraid there's no way we can tell you if your predecessor had done stuff outside JIRA with scripts, database triggers, or other code.

[Jobin Kuruvilla [Adaptavist]]

There could be multiple reasons. The trigger is usually a JIRA 'Issue Created' event but it could also be a workflow post function. And the plugin might be disabled, not working anymore etc. Hard to say without knowing anything about the design of the solution.

You might want to get help from an atlassian expert to debug, unless you have more details that you can share.

[Elijah]

Unfortunately I don't know enough about this project or Jira to know what to really ask at this point. But, I have until Wednesday to fix it. Oh the joy.

[Joe Pitt]

JIRA is a highly customizable tool. You're going to need someone with admin rights to go in and explore how your workflows and any added scripts, if any, are configured.

[Elijah]

There is no admin. There is only me. But I'll look into that section 'Workflows'.