Comments
-
Um, no, you had not said anything. You've just quoted the error message you get when someone tries to log in when they do not have permission, do not exist or have been deactivated.
-
Yes, the user isn't set up correctly - check their groups and that they've not been deactivated/disabled
-
No, that will just hit the login page. I'd hit the REST interface for something public - see https://docs.atlassian.com/confluence/REST/latest/
-
I think that just tells you that your web server is working.
-
Hit it with a REST call using curl - if it works, Confluence is there, if it doesn't, it's not running.
-
"facetious" means "being flippant when faced with serious issues".That is a completely inaccurate description of my attitude here.* You have a serious issue. * You have given us very little information to go on* I have asked questions in a way that tries to explain what information we probably need in order to help you*…
-
>ie we restored tables where the user information was missing This is probably the root of the problem. A flat restoration of any data in different versions of Atlassian applications is extremely unlikely to work. You have almost certainly destroyed at least one of the two systems. Your best option now is to shut all of…
-
I apologise for my previous comment - I typed and posted it before your follow-up which answers some of the questions
-
Please, be clear.- Latest version of JIRA implies 6.3, but it's worth stating it properly because you can get 6.4 as early access.- We do probably need to know what version you were on. "I believe version 5" is too vague- "Confluence was the new version but uninstalled it" is useless. What were you on, and what did you try…
-
I'm afraid there is too little information here, and it's very confusing too. We can't really help you until you can explain what you've really done. On the confusion side, JIRA and Confluence are separate systems, so I'm not sure what you mean by "an upgrade to add Confluence to our existing JIRA"? On the lack of…
-
We aren't support, most of us have other things to do, and we're not all in one time zone, give us time to catch up!I've not tested this, so I'm not sure, but I suspect the import expects the issue ID of the epic, not its name.
-
A filter has nothing to do with the data displayed, it returns a list of issues. If you want to get data from a filter, you need to put the filter through a report of some sort, such as the issue navigator. By dfinition, the issue navigator shows you issues. If you want project data in it, include the field "project" and…
-
Mmm, that is a bit of a bind. HSQL can, and does, fail catastrophically, and you can lose everything. Although, the xml backups you've got will at least make it easy to rebuild. I don't think pulling out and inserting a more recent and theoretically more stable version of HSQL is worth the effort though. I'd persevere with…
-
There's an underlying question here - why do you ask? Jira shouldn't be used with HSQLDB except for a bit of development and testing. So the version of HSQLDB is completely unimportant to you because you aren't going to use it for anything serious. If you're writing stuff that actually needs to know, then you need to stop…
-
If it's Cloud raise a support request, if it's your own servers, then start by reading the log file
-
Ok, definitely for support. https://support.atlassian.com
-
Does the list expand if you give it a while to load? If not, then I suspect this should be raised with Atlassian Cloud support, because the next thing I'd reach for is the logs, which they have access to (we don't)
-
Not in the UI, and probably not in your browser. However, where you'll need to start tinkering depends on what you're actually looking at. Which version of Jira are you using and what "projects dashboard" specifically?
-
You can't do it in JIRA without hacking code really, it assumes real users can change their profiles. Your idea about LDAP is a good approach, but you could also do it with Crowd or any other external directories.
-
Roles are not part of the Cloud user management stuff, they live inside JIRA. Log into JIRA as an admin and go to Admin -> Users -> Roles, and you should be able to see the current list of roles and add/delete/change them. (Note Cloud changes stuff sometimes, so if that instruction doesn't seem to apply, go to Admin ->…
-
There's no way to undo a deletion yourself. You've already done what I'd suggest and got in touch with support.Your account is not deleted though, Atlassian retain them for years for audit reasons, and I suspect getting it reactivated will not be hard. Via support ;-) Or possibly mailing sales-at-atlassian-dot-com with all…
-
Cancellation of what?
-
You need to add one of the custom field types that has a list of options - select, multi-select, radio button and check box are the obvious ones. If you add one of these, in the same way you added the version picker (which is explicitly designed to pick up the list of project versions), you'll find that it asks you to list…
-
You can only have one base url in Jira, so you need to decide which domain is going to be the primary place to run it and stick with that. You could however use Apache to rewrite urls so that it looks like Jira is working on several domains, but internal links and emails will still all be based on the base url
-
We're not official support, so there's nothing to close
-
That suggests the add-on data is not in the database. I think this patching approach is possibly losing something somewhere. Instead of your side-by-side method, could you do a full upgrade, as close to the standard process as possible? Recreate your current JIRA on a test machine (i.e. copy the installation and home…
-
If you didn't copy the full content of the home directory, the plugins won't be there on the disk. But, your data for them should be safe. You should find that re-installing them from the UPM gets you a "ok, found a licence for this, so I'm enabling it" and then the functions should jump back into life.
-
Sounds like you haven't copied all the data from the old home directory to the new one?
-
That should be fine, but read the release notes for 6.1, 6.2 and 6.3 carefully. And, of course, test it.
-
What do you mean by "swimlane counter" here? I've got a feeling you're looking at the columns estimates rather than numbers of issues...