Hello! I have created a sandbox to test jira emails. I can access the Service Desk project, but when I try to look at a different project where I Have escalated a ticket from the Service desk, I get an error that this project isn't available. I can see the project in my project list in the Sandbox. Any ideas what I can do? It's the orange DPS project that I am getting the error on when I try and open.
I suggest you start by looking at your permissions configuration for the project and the tickets in the project (project and project tickets have separate permissions so make sure you check both places - see inside project settings-summary page).
regards
Paul
Would the permissions change/be different from Prod to a sandbox? How come I can see the project in the list in the Sandbox? Thanks all !!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, the permissions in the sandbox can be different than your production instance. The thing to remember here is that the Sandbox is just a separate instance than your Production instance, and it is just labelled as sandbox for licensing purposes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I keep getting the "you can't do this in a free project" error. Should that be happening?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Permission set-up is defined in a default set-up somewhere.
I just happened to create a new project this afternoon and noticed that our default permissions were not usable when the project was created.
Only once I had changed both project and issue permissions schemes the new project was usable
We don't create many new projects so I am going to live with it.
You might want to consider fixing your defaults to avoid a future issue.
Happy Admin'ing ... Paul :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One of the few things I can think of here, is that the escalated user mailbox might not have permissions in the project you are trying to access. Sometimes the users need licenses and access with roles permissions in the project to access it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Become an effective Jira admin
Manage global settings and shared configurations called schemes to achieve goals more quickly.
Streamline Jira administration with effective governance
Improve how you administer and maintain Jira and minimize clutter for users and administrators.
Learning Path
Become an effective Jira software project admin
Set up software projects and configure tools and agile boards to meet your team's needs.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.