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
We upgraded a QA environment to v8.5.1 and uninstalled Jira Portfolio
Upon testing the upgrade we found that when we create an issue we don't get confirmation that the issue was created even though it was
Our tech team then installed Jira Portfolio again and just disabled it which fixed the create confirmation issue.
I am just wondering what else we need to do to be able to uninstall Jira Portfolio and not just disable it.
Thank you for reaching out.
Checking other similar cases, I believe that the error when creating issues once you have uninstalled the Portfolio add-on is happening because maybe some custom fields or app entities are still available on Jira Database tables after the removing of the add-on.
That being said, to uninstall and remove the custom fields completely, you can follow the steps below:
- Take a database backup first
- Find all the Portfolio custom field name and IDs from the custom field database table, under the class names com.atlassian.jpo.xxxxxxxx and com.atlassian.teams.xxxxxxxx. There should be 5 of them.
- Re-install Portfolio plugin and enable it (if you have not done so), this is so that you can remove the custom fields via the UI
- Run this SQL query to unlock the fields so that you can remove it (replace xxxxx with the IDs you found previously). There is no need to stop Jira to do this.UPDATE managedconfigurationitem set managed='false' where item_id in ('customfield_xxxxx','customfield_xxxxx','customfield_xxxxx','customfield_xxxxx','customfield_xxxxx');
- Once done, you can search for the field in the UI and delete all 5 portfolio custom fields. To ensure that you are deleting the correct custom field, take note on the custom field ID on the URL when you mouse over the "Delete" option, ie: http://<base URL>/secure/admin/DeleteCustomField!default.jspa?id=xxxxx, where xxxxx is the custom field ID
- After deleting the custom field, proceed and uninstall the Portfolio add-on by following the steps under "Uninstalling an app by removing its JAR file" section of the documentation below:
Let us know if the steps worked for you.