JIRA Customization doesn't work after Upgrating

[xinan liu]

I made a customization on JIRA 6.0.4 which can change the Project Panel. The original panel's content was Unresolved Issues, we modified it ro Open Issues.
We changed the class file "AbstractUnresolvedIssuesFragment" which located at "D:\Atlassian\JIRA\atlassian-jira\WEB-INF\classes\com\atlassian\jira\plugin\projectpanel\fragment\impl".
And 5 vm files "unresolvedissuesbyassignee.vm, unresolvedissuesbycomponent.vm, unresolvedissuesbyfixversion.vm, unresolvedissuesbyissuetype.vm, unresolvedissuesbypriority.vm".
But after I upgrated our JIRA to 6.3.5, it totaliy changed, I can't find the "AbstractUnresolvedIssuesFragment" and the 5 vm files.
Can any one tell me what to do now? Is there some documents describe this problem?

[Benito Picarelli]

Hi Xinan,

Assuming that you used the Repid method to upgrade JIRA, I'd see this page to check what were the checks needed before performing the upgrade and how (if) they can be recovered:

https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA+Using+a+Rapid+Upgrade+Method

I'd always recommend you to check this pages before upgrading JIRA to check what changed in it's configuration.

https://developer.atlassian.com/display/JIRADEV/Development+Resources

Regarding the support ticket, to be honest, I don't that we would be able to help you much further than this, since customisations are not really supported by Atlassian.

Cheers

[Benito Picarelli]

Hi Xinan,

Assuming that you used the Repid method to upgrade JIRA, I'd see this page to check what were the checks needed before performing the upgrade and how (if) they can be recovered:

https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA+Using+a+Rapid+Upgrade+Method

I'd always recommend you to check this pages before upgrading JIRA to check what changed in it's configuration.

https://developer.atlassian.com/display/JIRADEV/Development+Resources

Regarding the support ticket, to be honest, I don't that we would be able to help you much further than this, since customisations are not really supported by Atlassian.

Cheers