Comments
-
Well, that's pretty clear - the server does not have a working DNS, so it can't look up any other systems. You could put an ip address in for gmail, but that should be regarded as a temporary kludge to get it working for now. What you need to do is fix the broken DNS on the server. That's not really an Atlassian related…
-
@Karen O'Keefe- the 'bots here miss things, and are sometimes a bit slow to catch up. @Monique vdB usually manages to catch the ones they miss quite quickly, feels like she checks up on them daily, so expect a badge very soon. Edit - and there we go - she caught it between my "click to comment" and "typing a comment".
-
I'm a bit stuck on this - when I put a default value of "my random bit of text" in a message field for edit, I get that displayed on my create and edit screens. I suspect this might have to to to Atlassian support to debug, at https://support.atlassian.com/contact
-
It's the content that is the problem. When you ask for the content of a single-select field, you get "empty" or the selected option. When you ask for the content of a multi-select, you get "empty" or an array of one or many options - i.e. those selected. Your code needs to take the returned "value" and iterate through it…
-
This posting is 7 years old, but actually, Seraph is still in use if you want to do it that way. There are a lot more options now though, but they all boil down to "you need an SSO solution that works for your web application as well as Confluence". (Seraph is one of these, and Atlassian use it for their applications)
-
There is no Confluence 7, you just want to jump to 6.high (probably 6.13 as the latest). See https://confluence.atlassian.com/doc/upgrading-confluence-4578.html
-
Ah, I thought it might be. Confluence 6.5 and below have to use the database method of changing the password, they don't have a recovery function. Have a look through https://confluence.atlassian.com/conf64/restore-passwords-to-recover-admin-user-rights-936511358.html (and remember to remove the -D line if you upgrade to…
-
I am afraid you are still missing the point - Jira Core is what you used to get with Jira, Jira Software is what Agile used to add to it. A couple of functions from Agile were moved into Software because they made no sense to keep in Core when they were Software related functions.
-
Probably the owners and administrators of those Jira systems. I'm afraid here, we are a community of end users, we're not your admins, and we have less access to it than you do! I'd suggest asking colleagues or whomever asked you to use this ESS Jira who the admins are if you can't find it out from your local docs.
-
mmm, you'll notice that those were not "removed", they were chosen to be part of Software, not Core, although they did change shape a bit. No functionality was removed from Core, it was decided that as the applications split, some things needed to be in Software, rather than Core. So, while that quote is sort of…
-
Well done everyone! I'm going to admit to a slight bias though - I love the idea of a "boundless positivity" award, if nothing else, to help balance out my grumpiness. And although there was a lot of competition for it, I think the right people made it to the top!
-
Community isn't quite the place for that - I try to stay away from advertising any particular partner (including my own) in the interests of fairness. Also, I don't have a clue about the money - I leave that up to the sales people. Adaptavist will be more than happy to help you out, of course, but I'd ask you to get in…
-
The ps command shows us Jira running, but if it's not listening to you where you expect it to, the next step is to read the log file to see what it is doing. Have a look for <jira home>/log/atlassian-jira.log - this should give us some errors on the starting of Jira, which should tell us more.
-
Each email handler has a set of config that tells it what to do when it picks up an email. The main thing they need is the project and issue type (unless you just let it create the default issue type for the project) So, if you have 4 projects, each with 3 issue types, you are going to need 12 handlers to pick up all the…
-
3,500 users is well within the parameters of plain Jira server working fine, without data centre, and I've seen it cope fine with 40,000 although at that point, I would have much preferred to go to DC. If you're worried about load at this point, then I would be looking at factors other than users! But it's good to look at…
-
You should find out if Jira is failing by reading through <jira home>/log/atlassian-jira.log.If there's no smoking gun in there, try <jira install>/log/catalina.out for the Tomcat log - this should catch cases where Tomcat starts ok and looks like Jira is running, but it can't get Jira to start internally.
-
>To clarify the answer; JIRA 6.4 (and earlier) has functionality that was removed in JIRA Core. No, that is wrong. Some minor functions were tidied up, and some already deprecated stuff completely removed from the API, but no functionality was really removed from Core. If you are using Jira 6.4, you need to check if you…
-
Yes, a webhook sends content - it pokes data at a url. That is a very oversimplified way to put it, but I think it helps explain the basic concept of webhooks. We can't actually tell you a lot more. We have no information on what the other application's API is, what it is available over or what it expects.
-
My guess is that the issue type of "bug" is a sub-task type. These do not inherit the "epic link" from their parent (which I believe to be a howling design failure), even though they're part of an issue which does have it. Which means the clause "and not epic link =" will drop them out - as they have no epic link, it won't…
-
Did you select the new custom field as the "estimation statistic"?
-
There's not much we can do with that, except tell you that there is something wrong with the database. Could you read the <confluence home>/log/atlassian-confluence.log file for more detail? It should contain the error you've already given us, but with a lot more detail.
-
I'd start with https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html But, generally, you don't want to just play with them - you should have a specific need in mind and then go see if there is a way to do it. You can make a (repairable) mess of a workflow if you just tinker and some of the…
-
Ok, so it's running, but not serving - again, you'll need to read the logs to find out why, and check where it is supposed to be listening to you.
-
All you can do is make the assignee field mandatory. That is the "all or nothing" I think you're talking about.
-
There is no fix, nor really any "problem". You've destroyed the user information, so the system is doing the best it can with the data it has - rather than failing or displaying rubbish, it's displaying a placeholder to show that there was something there. To fix the existing data, you need to put the users back in…
-
I am not sure I understand what you are trying to do. For an evaluation licence, the easiest way to do it is to download and install Jira. When you run it for the first time, it will go through a setup phase, which includes asking you for a licence, and that screen has the server id you need on it, so you can nip off to…
-
Don't worry about the base url yet - it could be taking you back to https, but it won't stop you connecting to Jira. You need to get that working before you can change the base url. The error you have there is that Jira is not responding to the proxy. The usual reason for that error is that Jira is not running. You'll need…
-
Indeed, the way to "remove" an issue from a board is to change it so that it is no longer selected by the filters the board is showing.
-
I have no idea - there's a lot of config files. Your screenshot seems to have lost the file it is complaining about. If it was not the screenshot being trimmed, then your next step is to read the confluence log to see what the file is - should be <confluence home>/log/atlassian-confluence.log
-
You should be able to write a scripted listener that runs on issue create, update and assigned, looks at the assignee and works out which group to update the field with. You do have one possible logical problem to think through - imagine user N is in groups Y and Z - which group goes in your group field?