Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to create a Plan in Portfolio



I need help installing portfolio. Once it is installed, I can't create a plan with portfolio. 

portfolio jira.JPG

I also can't assign permissions to persons or groups within portfolio. 

Once I try to add permissions to my users, i get the following error

com.atlassian.activeobjects.internal.ActiveObjectsSqlException :There was a SQL exception thrown by the Active Objects library: Database: - name:MySQL - version:5.6.42 - minor version:6 - major version:5 Driver: - name:MySQL Connector Java - version:mysql-connector-java-5.1.47 ( Revision: fe1903b1ecb4a96a917f7ed3190d80c049b1de29 ) com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '0' for key 'PRIMARY'


 I tried reinstalling portfolio for JIRA, but I keep getting the same errors.

 I think the problem lies in the AOPERMISSION table which inserts a row with all null values except the ID_OTHER field which is initialized in 0.

I appreciate the help



1 answer

1 accepted

0 votes
Answer accepted

The problem was due to a bad MySQL configuration. 

We had the variable sql_mode = NO_AUTO_VALUE_ON_ZERO set.

Removing this variable was able to fix the problem.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events