Does updating a JIRA ticket's status automatically update the linked ticket's status as well?

[Mireille Gennaro]

What is the default behavior for JIRA tickets - does updating the status in one ticket automatically update the status for a ticket that is linked to it? One of my teammates claims that when she updated ticket A (core ticket), the "task" that was linked to ticket A was automatically updated as well. How can I verify this behavior and what is the default behavior set to do in JIRA?

[Alexey Matveev]

Hello,

By default a linked ticket is not updated. It means somebody customized your Jira with a plugin.

[Mireille Gennaro]

Thanks. How would I be able to confirm that a plug-in has been used to customize the process. Where do I go in JIRA to review this? 

[Nic Brough -Adaptavist-]

The fact it happened tells us there's an add-on or hack!  Jira has no code to upgrade anything on the other end of a link from an issue (the closest it gets is closing the last open sub-task on an issue can close the story if you're using Jira Software, but that's not even an "issue link")

As an admin, go to Admin -> Manage Add-ons and look for anything related to Automation, linking or Scripting.  There's a lot of ways to implement this sort of behaviour, so I am sorry, but we have to be quite vague in order to get you to check all the possible things it might be.

[Mireille Gennaro]

There is nothing in the add-ons that shows something related to automation, linking, or scripting. 

So my next question is - where do I go in JIRA to "unlink" having a child's status automatically be linked to a parent ticket since we can conclude there is some sort of add-on implemented in our workflow to do this? Admin - > Issues - > ? 

[Nic Brough -Adaptavist-]

We don't know, we can't identify the app your administrators have configured to do this.  To unlink it, we'd need to know what they've done to link it in the first place.

If you can't identify the add-on, then check your system for Listeners that might do it, and then go into the workflows for both child and parent and see if they have "post functions" that might be doing it.