Working with IssueLinkManager without history entries

[Tomáš Vrabec]

Hello community, 

I am in front of optimizing an routine job done in script runner. 

Basically, every night, it compares some custom fields with set off issues and recreates issue links between true findings. 

Thats working fine and as expected, the problem is, when users tries to reach the issue history.

Its flooded with system automation user entries of removing / recreating links.

My idea is, to 

1. Do not write history at all, but whole script is based on issueLinkManager.createIssueLink and issueLinkManager.removeIssueLink methods where I cannot find any way how to not write a history event.
2. After running the routine, at the end, run clean-up of history - simply remove all history event caused by system automation user, which perfectly fine by business need.

Any ideas how to achieve at least one of those?

Thanks, Tom

[Tiago Comasseto]

Hi Ken, seems that JIRA is trying to read the dbconfig.xml from E:\Jira_Home, one of the possible cause can be that the user running JIRA doesn't have permission to read the file, it's more common when JIRA is configured to run as a Windows service.

One other thing could be that the dbconfig.xml file is corrupted somehow, in this case you may delete it and recreate it using JIRA Configuration Tool.

I hope it helps.

Cheers