Why are there many database queries running when change the issue type scheme ???

mihan ayeshana

I can see many database chanages when chagning the issue type scheme

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39160', 'null', '10202', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39161', 'null', '10238', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39162', 'null', '10105', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39163', 'null', '10239', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39164', 'null', '10158', 'issuetype', '10052'"

INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39165', 'null', '10193', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39166', 'null', '10149', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39167', 'null', '10150', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39168', 'null', '10118', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39169', 'null', '10133', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39170', 'null', '10121', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39171', 'null', '10153', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39172', 'null', '10104', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39173', 'null', '10226', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39174', 'null', '10244', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39175', 'null', '11758', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39176', 'null', '10243', 'issuetype', '10052'"

"INSERT INTO configurationcontext (ID, PROJECTCATEGORY, PROJECT, customfield, FIELDCONFIGSCHEME) VALUES ('39177', 'null', '10498', 'issuetype', '10052'"

Why these lot of changes?????????

Norman Abramovitz

Hi,

The short answer is because there are.

When you change a issue type scheme, field relationship changes, issue relationship changes, the project meta data changes, etc, etc. The old relationships are removed and the new relationships are put into place. There are many records that need to be created.

Now could the Jira code be more efficient and use array binding, yes, but then it would need specialized code across the various databases. As long as the operation completes it should not matter.

In my opiinion changing the issue type scheme should not be a daily event, so if it is slower than other operations it should not matter.