You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
After migrating our instance from cloud to server, Jira is working fine, but Portfolio is not working due to some DB Schema errors:
ORA-00904: "plan"."RANK_AGAINST_STORIES": invalid identifier
We were not using Portfolio before (on cloud) - we are migrating to start using in Jira Server due to some features available only on this platform.
Detailed error message: https://drive.google.com/file/d/1Pr6L40hKIk6w9D_e3nMnUYnZ3-aJmsz0/view?usp=sharing
Hi @Mendel Liang ,
I followed the link you've provided above and opened a new issue ... but it seems to be this same site!
This is the new ticket I have opened:
Should I go to a different support site?
I believe if you press the "Create" button in the top bar of the previously linked website it should bring you here https://support.atlassian.com/contact/#/ where you will be asked to provide details about the problems you are facing.
As you fill out this form, it will ask you to provide your SEN (Support Entitlement Number). If the option to not provide this is selected, it may direct you to create a community post on this site instead of continuing creating a support ticket.
If you select the "Continue with this request option", or if a SEN was provided, then bottom of the form should have a button with "Submit support request" which will raise a ticket with our support engineers.
Portfolio for Jira Team
Thanks @Mendel Liang
I don't know why I wasn't able to open the support ticket with my SEN number, so I opened a "migration" ticket:
Please have a look if you can help us from there.
Hi @Ricardo Ardito
Check this topic, it seems you have the same problem. Basically, the accepted answer is to make "plan"(which I assume to be an alias) uppercase in your query