Comments
-
Ok, which analytics is this?
-
The state button does not really exist, it's a list of transitions with the end state displayed instead of the transition name. You need to alter the transition order, but I'm not sure the button takes any account of it.
-
None. At least, not until you enable either the built-in tracking (only suitable for small Confluences as it does not scale well), or get one of the analytics add-ons that do tracking. Have you enabled anything yet?
-
Different words, but the same broad meaning (according to my very old latin and google translate) and path through the login routine.
-
Set the number to be lower than the one you want it to appear before.
-
It works for me, I get all the fields, with a mandatory or optional flag set on them as well. But you do need to use the "expand" flag as documented in there.
-
The user needs "Edit" rights to update it.
-
The built-in database does not "run", it's a file and memory based system that is read at the time of startup. The error message suggests that the connection to it is not working, which usually means the database has failed in the case of H2. You can read the application logs for more, they will usually tell you where…
-
Go to download again, then look for "all server versions" and then look for "view all versions", which then has a selector for 7.x
-
It sounds like you're doing half an install, not using "manage applications". An install will not work, you've already got it installed. Go to manage applications and add software there.
-
The licences are bought independently of each other, although there's nothing to stop you buying them at the same time. There are downloads for Jira Core, Jira Software and Jira Service Desk, but not one that bundles all three. We usually recommend you use the Jira Software install and then add Service Desk. Yes, you can…
-
"Manage applications" in Jira can only add to the server you are running it on, it can't touch your local machine because it's only got access to the Jira it is running as part of.
-
I'm not sure "use manage applications to add it" is so hard.
-
How are you storing these cases and their status?
-
It sounds like you have a field called "Board", which is mandatory, but not on the create screen for the issues.
-
That was answered in your other thread already.
-
We're not support, we're a community of end-users of Atlassian stuff.
-
It's in Jira's admin section.
-
Nope, to see the issue, you have to be able to see the project.
-
Again, go to "manage applications" and add it. I don't know why you are not doing that.
-
Given the Cloud's poor design, I'd say a move to server is "forward" not "backward"
-
It's a number. 21 is smaller than 31. The actual number is not important, just that it's larger or smaller than another
-
Go to project admin, look for the "issue type screen scheme" and descend into it - there are several layers but each one does show you the next (as per diagram - you'll be working your way up through the central green screens)
-
How are you getting users into your systems? What directories are you using?
-
If you're having heat issues, you need to move to a server with hardware that can cope with the processes.
-
How are you wanting to do the SSL? With Tomcat or a proxy?
-
Go to admin -> users, where you will find you have more than 10 users, then disable the ones you don't want to have access.
-
Jira DC has three possible bundles, like the server version does. Core, Service Desk and Software. The Software and Service Desk bundles are nothing more than Core + <application> distributed together so you don't have to click "install" on the "manage application" page after installing Core. So, I don't actually know what…
-
If you change the default screens, yes.
-
You have not got Jira Software installed then. Try adding it from "manage applications"