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

Error when adding source to Portfolio Board

I have a user who is getting the following error when adding a source to a portfolio board:


java.lang.IllegalArgumentException: (no message)

  at sun.reflect.GeneratedMethodAccessor1997.invoke:-1
  at sun.reflect.DelegatingMethodAccessorImpl.invoke:43
  at java.lang.reflect.Method.invoke:498
  at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke:26
  at com.sun.proxy.$Proxy356.setProperty:-1
  at sun.reflect.GeneratedMethodAccessor1997.invoke:-1
  at sun.reflect.DelegatingMethodAccessorImpl.invoke:43
  at java.lang.reflect.Method.invoke:498
  at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke:136
  at com.sun.proxy.$Proxy356.setProperty:-1
  at com.atlassian.rm.common.env.issues.JiraIssuePropertyService.setProperty:316
  at com.atlassian.rm.common.env.issues.JiraIssuePropertyService.add:166
  at com.atlassian.rm.jpo.core.plan.PlanExcludeIssuesHandler.perform:32
  at com.atlassian.rm.jpo.core.plan.PlanExcludeIssuesHandler.perform:10
  at com.atlassian.rm.jpo.core.plan.RestructurePlanAction.apply:102
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler$2.apply:51
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler$2.apply:46
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inTransaction:62
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.access$000:11
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler$1.apply:35
  at com.atlassian.rm.common.persistence.DefaultDatabaseProvider$1.perform:30
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider$1.perform:41
  at com.atlassian.rm.common.bridges.jira.persistence.JiraDatabaseProviderBridge63.execute:66
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider.execute:34
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inDatabaseTransaction:28
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inDatabaseTransaction:46
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.restructurePlan:379
  at com.atlassian.rm.jpo.env.threading.AbstractTranslatedLongRunningTaskProvider$
  at com.atlassian.rm.jpo.env.threading.JiraLongRunningExecutorRegistry$1$
  at com.atlassian.rm.common.bridges.jira.threading.LongRunningExecutorServiceBridge63$
  at com.atlassian.rm.common.bridges.jira.threading.LongRunningExecutorServiceBridge63$
  at com.atlassian.rm.common.bridges.jira.threading.JiraSafeThreadService$
  at com.atlassian.rm.common.bridges.jira.threading.JiraSafeThreadService$
  at java.util.concurrent.ThreadPoolExecutor.runWorker:1142
  at java.util.concurrent.ThreadPoolExecutor$

=== Request ===

URL: /rest/jpo/1.0/plans/restructure/async/7980bc4e-3aa7-490c-888e-aa29da509ff6?_=1504620508062
Type: GET
Status: 500
Data: undefined

=== Client Info ===

User agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 
Local time: Tue Sep 05 2017 10:10:07 GMT-0400 (Eastern Daylight Time)

=== Plugin Info ===

Plugin build: 2.3.0
SEN: Unknown

=== System Info ===

JIRA Version: 7.3.8
Agile Version: 7.3.0-DAILY20170523023608


I am able to duplicate this error. The steps taken to generate the error are:


* Edit Sources for the Portfolio

* Add a scrum board, click Next

* Select a release from that board, click Next

* Select an issue, then click Done


We're still under an evaluation license until our purchase is completed. Has anyone else ran into this error?

2 answers

1 vote
María Atlassian Team Sep 07, 2017

Hi Chris, 
Could you please raise a ticket with support if you're still experiencing this issue?

Hi Maria,

One of our user have the same issue.

Have you link to share related the root cause ?



0 votes
Dave Atlassian Team Apr 26, 2018

What version of Portfolio are you using? This looks similar to this issue ( that was fixed in version 2.8.0.

Can't view this link

"It may have been deleted or you don't have permission to view it."

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

308 views 0 9
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you