Comments
-
You already have - there's a grey tick next to each answer which turns green when clicked to say "this is a useful answer".
-
What do you want from "analytics"?
-
If you have no access, there's nothing you can do because you can't change anything. You need to get their admin to shut down your account.
-
Look at the -Xmx setting in the environment your Confluence is running in. It is usually set in the setenv file under <confluence home>/bin (setenv.bat for windows systems, setenv.sh for non-windows)
-
Scripted fields are not fields in the usual sense of "something that holds and displays a data item". Because they are calculated, they're not stored on the issue in the database. So when their value is recalculated, there is nothing written to the issue, and hence no history to write. (Technically, this is not strictly…
-
It does support this, and absolutely fine. I've got access to dozens of systems via one email address. It looks to me like the problem you had was that you had not been enabled for access to the new Confluence when you tried to get in. That's what the message you got was telling you. In fact we have the opposite problem in…
-
Where did you set Confluence home to be? It must be in there for confluence to even start. You don't need to stop Tomcat, it only reads the file as it starts Confluence.
-
As I said, I think one of your users has added some data that can't handle. The \xE2..... string looks like encoding for an emoji, which Postgres (the database behind Cloud) can handle, but MySQL falls over on it. You can try setting a different encoding on the MySQL server (but this is not fully supported), or run the xml…
-
This doesn't seem directly related at first, but are you importing into a MySQL installation? I think one of your users has added some data that can't handle.
-
Given the question is 5 years old, I'd say things have moved on.
-
You can't, without code in Jira to expose it. It's not there because it's of no use to you.
-
There's a couple of ways to do it, but I use brute force and go edit the config file directly. Look in <confluence home> for confluence.cfg.xml - it's not long or hard to edit, and it is that one single place you need to edit.
-
On Cloud, I'm afraid you have signed up to take changes as Atlassian want to roll them out. In your screenshot, it looks like you have not created any Epics or versions, and I would guess that you have not added the time-tracking field to the screens for the issues.
-
What status are the sub-tasks in?
-
I suspect you want project = "some name" or assignee in (Joe, Mary, Julie)
-
You can, but I don't see much point, as I can't think of a use for knowing the status new issues will go into.
-
It's actually comment you need, not "edit". Try jira.permission.comment=denied instead
-
You will need to do a LOT of coding to find the usage of a group like this. It's one of the reasons we recommend using roles as much as possible instead of groups - you rarely change those, just add and remove users and groups to the roles. The workflow changes will be particularly hard - they are stored as xml in the…
-
Please, don't use the database. It's not intended for reporting, so you'll be making some torturous and complex SQL for even the most simple of queries. There are no functions to expose any of the raw database tables anywhere in the UI, including the dashboards. I also notice you mention "cloud" in the tags, which makes…
-
I would suggest disabling them all for the upgrade, then when you've got the new version up and running, going into the UPM and upgrading any that say they need it.
-
Check your services and listeners, but the reason I usually see this is incoming email being processed repeatedly - when Jira can read the emails, but not delete them, it will process the same ones over and over.
-
Again, get Jira Software. Greenhopper was renamed "Agile" years ago, and that was converted to an Application when Jira 7 was restructured.e
-
You need to talk to your server administrators about a route to transfer files between your servers.
-
You can't do it in Jira, beyond showing the users the JQL behind the board. There could be one or many reasons an issue is not there and it could be because it's not included or excluded.
-
I'd start with Jira Software, as that's what it is for.
-
How have you implemented tests in Jira? Which app? Or is it just an issue type?
-
No, because the problem is with your AD/LDAP.
-
Your screenshot is of a user who is not deactivated. I don't think you are talking about the active/inactive flag in Jira. What do you mean by "deactivated"?
-
You need to give it the right username/password combination. There's nothing trying to be clever or different from other applications in the code, it really is just checking username and password match what it has for the account. If a user gets their password rejected, then either they have given it the wrong combination,…
-
Please stick to the supported JDK versions - using unsupported ones will give you problems for which you simply are not supported, and any call for help is going to get you a simple "run it on the right version, then see if you still have problems"