Installed Portfolio add-on on JIRA server but none of the pages open up. Gives a 404 resource

[Ashwin R]

Portfolio Add-on from market place on JIRA Server 7.13.

Completed Re-index as suggested. 

As Admin, logged in to add users access to portfolio but no page found error

[Ashwin R]

[Resolved] All modules did show enabled correctly. 

For some reason the user used to create JIRA application tables did not have access to the  tables created by portfolio add on. Once we have the user access to the tables, all functionality worked. 

It worked for other add ons from the marketplace, so this could be an isolated incident. 

[Earl McCutcheon]

Hi Ashwin,

Thanks for the confirmation on the cause, glad you found it so fast.

Since it was a DB permission issue I would also recommend doing a follow up check on DB configs just to make sure everything lines up with setting in "Connecting Jira applications to a database" for your DB type.

Regards,
Earl

[Wansze Kong]

@Ashwin R   Can you please elaborate with relation to the "JIRA application tables that did not have access to the  tables created by portfolio add on"?  We are experiencing a similar issue in our Jira instance and would like to know which tables you are referring to as well as the steps you took to resolve this matter.  

Any assistance you can provide will be much appreciated.

Thank you,

Wansze Kong-Chan

[Earl McCutcheon]

Hello Ashwin,

When you get a 404 on a page load in portfolio it usually indicates one of the app add-ons is disabled or possibly a sub module in the app is disabled, as covered in this feature request to provide better error messaging on when this occurs this:

• https://jira.atlassian.com/browse/JPOSERVER-2310

Check out the three portfolio Apps to verify the base app and all the modules for the app are all enabled, and let us know if this is the case:

• Portfolio for Jira
• Portfolio Live Plans
• Portfolio Team Management

Also, since you noted this happening right after the install there could be another app installed that is causing a conflict on the portfolio module startup, and increasing the plugin wait time as described in "Add-on Tips and Tricks" could help alleviate startup conflicts.  But I would also recommend checking the logging to see if there are any explicit errors that could help narrow down what occurred at the time of the install.

Regards,
Earl