Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Error while creating the isue: null

I have this error then I try to create new issue (task). Where is the problem?

5 answers

1 accepted

0 votes
Answer accepted

The solution was to delete one of a post function in "Create issue". Probably it was added by the plugin which now doesn't exist.

In Customer Portal I have this error: Error!

Not able to create issue via this Service Desk.

0 votes

You'll need to explain your setup, and I'd strongly suggest reading your log file, as that will tell you where the "null" is coming from. Even if it's a techy thing and you can't read it, we can't help you with just "Error" or "null" - we need to know what it's reporting in the background

I've look through logs file and... a don't know what am I looking for?

I don't change anything in my setup. That error comes from nowhere...

The problem is only in Service Desk...

OK, which logs I have to search?

Your log files will contain errors telling us what is happening when you get this error on-screen. The logs will be a lot more detailed and technical. I'm afraid just saying "error" without explaining what you are doing, what you have set up or anything else you are seeing is not going to get you far, you need to look at the resources you have to help you - logs, repeating the problem, examining the configuration and seeing what it *might* be

The application log. Easiest way to find it is look in Admin -> System information, which will tell you the full path to the file

2014-05-11 20:40:38,779 FelixDispatchQueue ERROR [osgi.container.felix.FelixOsgiContainerManager] Framework error in bundle com.atlassian.plugins.atlassian-whitelist-api-plugin
org.osgi.framework.BundleException: Unresolved constraint in bundle com.atlassian.plugins.atlassian-whitelist-api-plugin [111]: Unable to resolve 111.0: missing requirement [111.0] package; (package=com.atlassian.activeobjects.external) [caused by: Unable to resolve 26.0: missing requirement [26.0] package; (&(package=com.atlassian.plugin.osgi.bridge.external)(version>=2.6.5)) [caused by: Unable to resolve 5.0: missing requirement [5.0] package; (package=org.springframework.beans) [caused by: Unable to resolve 2.0: missing requirement [2.0] package; (&(package=org.apache.commons.logging)(version>=1.0.4)(!(version>=2.0.0))) [caused by: Unable to resolve 9.0: missing requirement [9.0] package; (&(package=org.slf4j)(version>=1.6.4))]]]]
at org.apache.felix.framework.Felix.resolveBundle(
at org.apache.felix.framework.Felix.loadBundleClass(
at org.apache.felix.framework.BundleImpl.loadClass(
at com.atlassian.plugin.osgi.util.BundleClassLoaderAccessor$BundleClassLoader.findClass(
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at com.atlassian.jira.plugin.DefaultComponentClassManager.constructEvenIfNotEnabled(
at com.atlassian.jira.plugin.DefaultComponentClassManager.newInstance(
at com.atlassian.jira.service.OfBizServiceConfigStore.loadServiceClass(
at com.atlassian.jira.service.OfBizServiceConfigStore.instantiateServiceContainer(
at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceContainer(
at com.atlassian.jira.service.OfBizServiceConfigStore.getAllServiceConfigs(
at com.atlassian.jira.service.DefaultServiceManager.loadServices(
at com.atlassian.jira.service.DefaultServiceManager.ensureServicesLoaded(
at com.atlassian.jira.service.DefaultServiceManager.getServices(
at com.atlassian.jira.upgrade.ConsistencyCheckImpl.getServices(
at com.atlassian.jira.upgrade.ConsistencyCheckImpl.ensureSingleService(
at com.atlassian.jira.upgrade.ConsistencyCheckImpl.checkMailListenerAndService(
at com.atlassian.jira.upgrade.ConsistencyCheckImpl.checkDataConsistency(
at com.atlassian.jira.upgrade.ConsistencyCheckImpl.checkConsistency(
at com.atlassian.jira.upgrade.ConsistencyCheckImpl.initialise(
at com.atlassian.jira.startup.DefaultJiraLauncher$
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(
at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(
at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(
at com.atlassian.jira.startup.DefaultJiraLauncher$
at com.atlassian.jira.startup.DefaultJiraLauncher.start(
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized( <+5> ( ( ( ( (
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$ Source)
at Source)

You have an idea where is the problem?

You've probably got a broken plugin (what plugins have you installed? Are you 100% sure the versions you've installed are compatible with your version of Jira?).

Or you've amended something in the installation that has broken it - have you made any tweaks? How did you install it? Have a look at the system information page and check the classpath, version of Java, and that the "modified files" list is nice and short.

But, first, try clearing the plugin cache -

I don't use confluence ( I only use JIRA and JIRA Service Desk. How to clear cache in these two?

Oh heck, I'm really sorry, I'm working with a broken confluence at the moment and have that on my mind.

Clearing the cache in Jira won't help, you'll need to look at the other two points.

I have these add-ons:
Gantt-Chart Project for JIRA - Free
Analytics Client Plugin
Atlassian Chaperone
Atlassian Universal Plugin Manager Plugin
HipChat Core Plugin
HipChat for JIRA
InProduct translation for JIRA
JIRA GitHub Issue Importer
JIRA iCalendar Plugin
JIRA Importers Plugin (JIM)
JIRA Polish (Poland) Language Pack
JIRA Service Desk
JIRA Service Desk Polish (Poland) Language Pack
JIRA Toolkit Plugin
JIRA Working Hours Plugin
Redmine Importers Plugin for JIM
Support Tools Plugin

Ok. Try turning them all off, except Service Desk, Atlassian Chaperone, the Universal Plugin Manager and the Support Tools Plugin (not uninstall, just disable them)

I did it and nothing has changed: Not able to create issue via this Service Desk.

Now have this message when I try to create new issue as administrator or as a Service Desk Customer: Not able to create issue via this Service Desk.

Has the error message in the log changed though?

I think we need to look at your overall installation though. How was this instance created? What have you changed? What does the system information page say about "modified files", your version of Java, your version of Jira and the versions of the plugins you have?

Instance was created by my host company on my server.

Everything is working properly and than problems come from nowhere. I have a information to chance HSL DB for MySQL and we did it yesterday. Everything is working but without Service Desk.

System information:

- modified files: [Instalation type: Standalone]

Wersja Java 1.7.0_25
Dostawca Java Oracle Corporation
Wersja JVM 1.7
Dostawca JVM Oracle Corporation
Wersja implementacji JVM 23.25-b01
Java Runtime Java(TM) SE Runtime Environment
Java VM Java HotSpot(TM) 64-Bit Server VM

Sterownik bazy danych MySQL Connector Java mysql-connector-java-5.1.30 ( Revision:

JIRA version:

Wersja 6.2.3
Numer wersji 6260

So "I don't change anything in my setup. That error comes from nowhere..." is wildly inaccruate and we could have been chasing completely the wrong thing. You've made an infrastructural change and not considered that could be part of the problem?

It's the right thing to do - HSQL is not suitable for production, but the migration is the FIRST thing you should have said, not said you haven't change anything.

So. How did you do the migration? What did you change as part of the migration?

Now I have a new problem :( In URL http://IP_Adress:8080/servicedesk/agent/klient_ID/customer/sd-servicedesk-request-types-listI have a blank page with no oportunity to view or edit anything

I've made backup (XML) and hosting company create a new installation of JIRA. Then I use setup wizard and set MySQL database and then I import backup (XML). That's all.

I've checked the integrity in http://IP_adress:8080/secure/admin/IntegrityChecker.jspaand there is a problem with:
Check workflow integrity <input type="checkbox" name="integrity_check_4_6" value="6" checked="checked"/> Check you have entered are correct workflow statuses

ERROR: XX-84 - workflow entry with id 10229 has an incorrect status. (JRA-4241)

Suggest an answer

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

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

977 views 31 33
Read article

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