I'm trying to import a project and the validation is failing with an error that states: "The Issue Link Type 'Gantt Dependency' has style 'Gantt' in the backup, but has no style in the current system."
I have no idea what this means. I have an issue link called Gantt Dependency, I believe it was added to our system when we were previewing the Gantt Chart plugin. However, I have no idea what this link is used for, how, or what the heck a style is in this context.
If anyone can help with this it's really obstructing my ability to finish my migration to a new JIRA server. Thanks.
I couldn't fix this, I just deleted the link entries from the database for the problem links and created a new backup, and that imported ok.
As an alternative if you are comfortable with databases, you can add the 'style' directly into the 'issuelinktype' table. Thats what I did and had to restart the JIRA service and then it was recognized properly
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Update the entities.xml to remove the style:
<IssueLinkType id="10020" linkname="Gantt Dependency" inward="has to be done after" outward="has to be done before" style="Gantt"/>
OR add style to target database
update issuelinktype set pstyle = 'Gantt' where linkname = 'Gantt Dependency';
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same issue:
I wound up installing JIRA Home Directory And DB Browser add-on in the target instance then issuing the needed SQL updates for each of the show-stopping errors:
{example}
UPDATE ISSUELINKTYPE
SET PSTYLE = 'wbsgantt_dependency_EE'
WHERE ID = 10201
your ID may be different.
Then had to stop and restart JIRA for that to take effect -- problem was solved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you can temporary install the Gantt Chart plugin on the target instance to workaround the issue. or else you will probably need to remove the entities in the XML backup which will take a lot of effort.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had that same thought when I saw the error message, so I did an install of the plugin to try to fix the problem, but it didn't work. Thanks for the idea, I have a ticket in with Atlassian so hopefully they'll be able to point me in the right direction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.