Issue not displayed on board

[Margriet Kapteyn]

I have created an issue called 'Cagdas Mandali'. When I go to Projects > List it appears with a status Contacted. However, when I go to the board, it is not in the column for status Contacted. When I search on 'Cagdas' it doesn't appear. (All other filters have ben cleared)
The same is happening with another 3 issues that I added recently. 

[JamieA]

Feel free to create an issue. Like I say though, I do not currently plan to resurrect this functionality.

Yes you should just be able to create an account on that cloud instance... if that doesn't work please can you contact Atlassian support, as they seem to keep reconfiguring it such that it's unusable.

[Mikael Lejdstrom]

Ok, I have to be more clear, it's very easy to explain. Wat I mean with "jira project trole list" is: Open a jira project's summary page as jira project/system administrator. Choose "roles & more" and you will see which users and groups that have specific roles in the project.

The users in 9 projects 1st time and the 12 projects 2nd time were deleted from the roles in this project. This happend when we used the function "Renames a user ID" in the "Builtin Script Runner" menu with the merge option in our production jira database. The rename worked fine but then this happend afterwards which I consider very serious. People cannot work if we not immediatly restore the user lists from a backup. So we cannot use this function any more, and we have used scriptrunner for years without problems. We have jira logs and also an anonymised database which you can use to analyse this problem The problem is to get access to your jira project for script runner so I can provide you with the logs. I.e. to join jamieechlin.atlassian.net. Is this possible ? FYI we are using jira 5.2.4 and groovyrunner 2.1.12.

[JamieA]

Can't seem to add an answer.

I've never seen that before, and I'm not really sure what you mean by "jira projects role list". This particular function has been removed from the recent releases... it was done before Atlassian introduced embedded crowd, and it needed a lot more work to make it work with Crowd.