Some users can create a new version in the project while creating the ticket and some cannot.

[Rebecca Wise]

I have 2 different projects that were set-up to be identical to one another (but using their own independent workflows, screens and fields). Users in one project can add a new version to their project while creating the ticket. Users in the other project get an error message that the version does not exist.

Why can users in one project add a version on ticket creation while the users in the other project cannot?

[Nic Brough -Adaptavist-]

To create a version, you have to have project administration rights (and/or a kanban board "release").  Check the permissions of the two sets of users.

[Rebecca Wise]

They both have project administration rights to their own projects.

[Nic Brough -Adaptavist-]

Ok, be completely bloody-minded about it.  Can you get a user who can not add versions to go to the project administration screens, select versions and see what error they get when they add a new version, or tell us if they can't because the option is not offered.

[Meg Holbrook]

Two things I can think of are that fixversion isn't on the edit screen OR the resolve issue permission is not set to allow access. (Versioning is included in this permission)

[Rebecca Wise]

Both projects have only one default screen. I've checked the permissions and the resolve issue permission is set so that everyone has access to do it.

[Meg Holbrook]

Are the permission schemes identical as well? 

[Rebecca Wise]

Yes, the permissions are identical.