Comments
-
The account 6479463@gmail.com is not the one you have set up in the email connection. You'll need to correct the outgoing email addressing.
-
"They are fine" tells us nothing. What are they doing? JIRA 4 doesn't work with Java 8, but I'm not sure why that matters.
-
And nothing else gets written to the logs? What are the cpu, jira process, disk and memory doing? Are they active?
-
I don't know, you've not told us how much memory you've got. But it probably is, as you only need 1Gb heap space for a small server. You just need to get a fast local disk attached and you'll be fine.
-
Ah, I've seen this a couple of times. JIRA is immensely slow to start up, but works fine once it gets there. I've never found the cause, but if you leave it for an hour, does it complete?
-
But what does the log say it is doing? What are the bottom few lines? Is it not writing anything? Any errors?
-
What does the log say it is doing?
-
Look at the project configuration. First check the default assignee rules to see who is set up as the default assignee, then the permissions to see who can be assigned issues. Then put the default user in the roles or groups they need to be in to be assigned an issue. Or turn on "allow unassigned issues" in general…
-
This needs to go to Atlassian Clouod support - https://support.atlassian.com/contact
-
Have you got a design for it that works with swimlanes?
-
You can't "undo" the changes, you'll need to correct the data on the issues you made the mistake on. You say the issues you've damaged were closed but are now open. That suggests that they are in the wrong status. To fix that, use bulk edit to transition them back to a closed status.
-
Jira has no functions for that. There's a list of users, and they are in groups and roles. The permissions say who can do what with issues, but there's nothing to hide users from one another.
-
You'll need to log into the proxy. Sourcetree as a client application does not need to be aware of the proxy, the operating system should be handling it. I don't get why you're doing this on a server either.
-
No, system info is just a snapshot taken as the page renders. It may be just that one process that's going too high. Remember it allocates in chunks, not the whole lot in one go. Is it possible to temporarily increase your heap size by say .5G? The -Xmx setting in setenv.sh/bat
-
Ah, you're using wild or quick searches that go across fields. Simple answer is "don't". Or if you're going to look for a something that is not a JIRA issue key, use "and id != <what I'm searching for>"
-
You'll need to contact Atlassian, as I already said.
-
Not your innodb log file, it seems to need more heap memory in the JVM.
-
I don't understand the question. It's two methods to get one result. You don't have to use the id.
-
There are other add-ons that might be able to do a scripted field for you, and some that might provide an explicit "users who did transaction" as well. I've always got ScriptRunner around, so I've not looked for them
-
As Sourcetree is a client application intended to be used by people interactively, this sounds like a very odd requirement. However, it's just using whatever network connection you've got on the machine it is on, so a proxy should be invisible to it, as it's a client.
-
You will need to contact Atlassian on https://support.atlassian.com/contact If your owner is still with you though, all he needs to do is add more billing and technical users to the account, and they can remove him.
-
Please re-read it again, there's no mention of new steps.
-
See third paragraph of my answer. Although you'll need a multi-user-picker, and "add to list" code.
-
It's the same answer - Karan and Nabiha stopped posting here because they were asked to give the results of a search, and then found their tests when they ran the search.
-
Well, you can turn off the modules, but you aren't going to get far without code. "No dashboard or reporting" though is a terribly broken requirement. The whole point of a tracker is to track things, which means you want to report on them. Just removing the reporting links won't stop the users getting to the reports, and…
-
You will need to find or write a bit of code to do that. The gadget can work on users, as you can tell by looking for "reporter" or "assignee" in the list. But "last person who moved the issue through a transition" is not a field in JIRA. You'll either need to create a single user field for it, and then change your…
-
You're in the wrong place, your question has nothing to do with Atlassian products.
-
My guess is that your production system is hooked up to an external user directory and gets most of its users from there? You'll need a test copy of that in your Staging environment.
-
What is going wrong with the download? What's the error? Once you've got a download, there's documentation - if you get stuck with that, let us know which doc and where you're stuck.
-
No, you should make a copy and upgrade it. Confluence 6 is very very different to 5, and you would miss files or make others redundent. 5.4 to 5.4.3 probably won't have a problem, but don't bet on it! Upgrade...