nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What happens if columns jiradb.issuelinktype.inward and jiradb.issuelinktype.outward are made null?

unknown

Could you please provide what would be the impact if the columns jiradb.issuelinktype.inward and/or jiradb.issuelinktype.outward are made null in jiradb.issuelinktype table for particular issuelinktype?

We have few tickets which are linked because of gantt chart add on.The issues are linked with no logic.

Scenario: issue A is linked to issue B saying issue B must be done after issue A

Issue A and Issue b are never sub tasks to each other.

Thanks

Accepted answers

Nic Brough -Adaptavist-

You will find Jira breaks in interesting ways.

Simple answer is that you should not even be looking at the database, it's complex and not intended for you to know or care what Jira and its Apps do in there.

All comments

Nic Brough -Adaptavist-

You will find Jira breaks in interesting ways.

Simple answer is that you should not even be looking at the database, it's complex and not intended for you to know or care what Jira and its Apps do in there.

unknown

Hi @Nic Brough -Adaptavist-

Could you please elaborate how jira will break on changing the values to null on the said columns?

What about the impact when we change the values to null for columns jiradb.issuelink.soruce and jiradb.issuelink.destination in jiradb.issuelink table?

Thanks

Nic Brough -Adaptavist-

Leaving nulls in the tables will cause the code that expects data in there to return nulls, which are then not handled by code.

Please, stop looking at the database, you really don't need or want to read it, and you absolutely must not even think about writing to it - you will wreck your Jira if you write to it without knowing exactly what you're doing.

unknown

Hi @Nic Brough -Adaptavist-

I agree that jiradb.issuelinktype table values cannot be made null since it is an important table or master table. However, jiradb.issuelink table is table where data is populated because some transaction or by execution of some program.Why can't we delete a record from jiradb.issuelink table so that a existing links between 2 issues can be removed.

Could you please let us know if a such a thing can be achieved by writing a script

where the script will have a statement to take backup and then delete a record for a particular ticket, test it if the links are removed and then delete all records which are linked because of a proragm such as Gantt chart?

If you agree with this, I can share the queries I prepared and Please verify them and guide us accordingly

Kindly let me know your inputs.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server