nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error while creating the isue: null

sledzinski

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

Accepted answers

sledzinski

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.

All comments

sledzinski

In Customer Portal I have this error: Error!

Not able to create issue via this Service Desk.

Nic Brough -Adaptavist-

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

sledzinski

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

sledzinski

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

sledzinski

The problem is only in Service Desk...

sledzinski

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

sledzinski

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.

sledzinski

Any ideas?

sledzinski

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)

sledzinski

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.