We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file.
The error is normally caused by a post function in the Create Issue transition.
Sometimes a post function requires a plugin that is disabled or a postfunction is positioned on top of "Create issue originally" and has problems on runtime, thus the issue can't be created.
If post functions look ok, contact support at support.atlassian.com
Correct but not entirely correct.
In my case the post function was set correctly - the problem was with the the custom field configuration. I resolved the issue by identifying why a field was not displaying in a screen. From there the rest was easy.
However it would be far better to have a non ambiguous message saying exactly what the problem was. I sat here for 10 minutes before copying the error message and googling it.
Thanks for pointing at reason for the issue.
I verified that postfcuntions and plugin used were proper.
But the background indexing was not going further due to index file corrupted. Hence I did "Lock JIRA and rebuild index".
After reindexing it worked again.
How reindexing is related to postfunction using some plugin.
Thanks in advance,
I've caught similar error and catched error in log file - jirasoftware310517123036-stdout.2017-06-16
com.atlassian.jira.exception.CreateException: Can not assign issue to nonexistent user: waiting.
waiting was my fake user, mentioned as default assignee in project setup.
I've change project setup to have no default assignee (UNASSIGNED),
deleted user "waiting" - and got this error.
I've created it again, and everything is working now.
But I still have question - what's wrong with project setup? It's still no default assignee, but all new issues are assigned to "waiting"
Help me pls :)))
I am facing a simmilar problem, I am traying to copy the value of a Project picker field and to another.
But is not possible due to the fact that this is a advanced field in JIRA.
So before show the information JIRA modify the string to a kind of html hypertext.
Also the same message errors aperas.
We have the same issue
In all cases I am seeing a duff post function. These include
Null "Fire a Generic Event event that can be processed by the listeners" entry
Clearing the resolution status before the step "Creates the issue originally"
We started to see these errors after an upgrade (from v7.1.9 to v7.6.4) and I suspect that the bad post functions were simply ignored in the earlier version.
I have no way of finding if other workflows have the same issues, I have to sit back and wait for complements from the users.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs