Which Foreign Key constraints does JIRA enforce in the Database (MySQL)?

We have recently converted a JIRA 4.1 Installation from using MyISAM to using InnoDB. When doing the same for Confluence, foreign key constraints have to be added. However, it seems that a fresh installation of JIRA 4.1 does not create any foreign key constraints at all.

When upgrading to 6.0, only a few constraints are created for Active Objects, but none for "internal" JIRA Tables.

The information on the web is very slim, only a pdf by a third party can be found easyily, which claims that "the JIRA database does not enforce foreign keys and does not actually use the same data type for foreign keys in all cases".

Is that correct? Do I need to create no foreign key constraints after switching from MyISAM to InnoDB?

1 answer

no, you haven't ... The correlations were implemented internally in JIRA

I am willing to accept the answer if

  1. You reformulate "no, you haven't" - that is no sentence and has no reference to the question
  2. You give a reference

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,301 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot