Comments
-
Confluence-server and Confluence-cloud are two different products. You can run Confluence-server on any machine (that meets the requirements for running it) you want to. Whether that server is in your house, in your office under a desk, in your data centre, in someone else's data centre or in "the Cloud" (Which can be…
-
There's no logs here I'm afraid - could you try showing us the text of the errors?
-
SEN is your "support entitlement number" - it's unique to your licence. Jira does not have SKUs in the usual sense, much like almost all software. It has a deployment type - Cloud, or Server/Data-Centre (with a version)
-
Ok, then the only thing I can think of is that the name you've given there is not their login id.
-
You can persuade the Tomcat to run on port 80 (or 443 for https), which will make it work as almost every browser will make that assumption by default, based on the protocol! However, it's generally better to use a proxy. Apache, Nginx, Lighttpd etc can all take an incoming "port 80" and proxy it to "your confluence:8090"…
-
Yes, send it complete JSON.
-
Yes, I think you have it right - 25 or 50 Agents for JSD, plus 10 or maybe 25 Confluence users. If you set up Jira and Confluence to use the same user directory, this becomes very easy to manage as well - you could have a group called "KB Author" which is used for write access on Confluence and Agent access in JSD, and…
-
Are you using an internal user directory or an external one?
-
Does your DNS also map the port? If not, then try http://wiki.companyname.com:8090 . You'll probably need to check all the firewalls and network routing too - try a tracert to the FQDN to check if you can get there.
-
No. You need 50 licences for JSD (although I'd take a look at that - do you really want 50 Agents? Or is it more like 50 developers for Jira stuff, and maybe 5 agents?), and then 10 licences for Confluence for the people creating and editing pages.
-
You can not just "set" a status, you must transition your issues through the workflow to the desired status.
-
Your JSON does not appear to be complete. The first message in your original question tells you that. The second error is probably a direct consequence - if the JSON is not complete, Jira doesn't know how to read it, so it discards it, and then tells you that it can't import data that it doesn't know about.
-
I was - lithium padded it when the data was brought in from the last version of this site! But glad you've managed to get there now!
-
It's what you are sending to Jira over the REST call you make.
-
Ok, then it is completely unclear as to what you are doing here. Forget this soapui, it's an unknown. Your java is making a REST call to Jira and is getting a "no content to map" type error. This suggests your call does not have well formed data in it. You'll need to fix that.
-
This isn't Confluence, this is Lithium. Confluence doesn't have padding bugs.
-
Only for the knowledge base spaces they get access through Jira Service Desk.
-
It's what the error message said. 6.4 is too low a version to import from. You'll need to upgrade that to 6.7
-
Jira does not have a Soap interface since 6.3, so could you confirm that you're looking at such an old unsupported version? The REST response is probably correct though, it sounds like your data is not complete in the call.
-
https://confluence.atlassian.com/doc/upgrading-confluence-4578.html Although you may struggle with such an old Ubuntu.
-
The second link works fine, the first has a couple of characters added by this platform (it's a known bug) - try it again, but lose the %A0 on the end of the url
-
You need a separate Confluence licence. Although you don't need to match numbers. For example, I know of a site with 10,000 customers (free), 500 Jira users including 10 Service Desk Agents, and 100 Confluence licences (10 for the Agents to do KB work, and the other 90 used by people writing docs)
-
It depends on what your data points are. I used an example of "status", which you can easily get lots of reports on in plain Jira. I don't know what your data is, so I can't tell you if Jira can report on it.
-
That looks pretty clear to me - that user does not exist in your system.
-
This is supposed to be difficult, because it's not the way you do Scrum. The concept is that in a Scrum, you commit to delivering a specific set of stories within a sprint. At the end of the sprint, the success criteria is very simple - either you completed a story if you did not. You're not supposed to split a story…
-
It depends how far through the install gets. Start with a look at <the jira home you chose>/logs - if it exists, then atlassian-jira.log is the one we want. If it's not there, then it should be <the jira installation directory you chose>/log/catalina.out (but also check that directory for other logs, there could be more…
-
The fields aren't right-justified, they're left-justified in a column on the right-hand side. As Brittany says, there's no way to change that, it's part of the new view.
-
I'm afraid there's not enough detail in that response for us to help you. We don't know what you are doing, what you have tried, or where you have diverged from the documentation.
-
No. Do not. The query required for even the most basic issue download is hideous and this way lies madness.
-
Split the story into two - one for backend, the other for frontend