Comments
-
I've seen this caused by two things in the past. One is that the database is not ready to serve at the time Confluence needs it. The more common one is that your hosts file is incorrect. See if you can ping your own machine from itself, using the host name, i.e. if your machine is called "dave", try ping dave Does it come…
-
Copying the old file back might not be the right thing to do, as it may have changed as you upgraded. Also, server.xml does not go in jira/bin, it's for the <jira install>/conf directory, and you should take a look at cacerts and setenv.sh as well, in case those have changed.
-
Those don't seem to be errors, more like commands. Could you show us a bit more?
-
It should have installed startup scripts in /etc/init.d/ but I don't think it flags them for auto-starts them under debian 9. systemctl | grep -i jira should tell you the current status, and what the service is called, then you should be able to use systemctl enable jira.service
-
All the logs we need should be under <jira home>/logs. Check the system information page under admin if you're not sure where <jira home> is on your system.
-
The Scripted field option does mean that you have complete control over what you expose. In some cases, it is a security problem for a user to even know there's a link to issue X, but that's not common - the usual problem is that links expose summary and other information. But with SR, you've complete control over what is…
-
That does sound like an automation, trigger or listener doing something with your issues. Do you know what it's trying to tell you? (I mean in general - is it telling you about failed builds? Or an internal process, or a failed SLA, etc) Can you check for Automations, Listeners and so-on?
-
There's no setting for it - a link that leaks information that the user would not normally able to see is absolutely the wrong thing to do in security terms. I'm not aware of add-ons that would directly allow you to unsecure your links, but if you've got one of the scripting plugins, or a developer to hand, you could write…
-
This is where I'm stuck. What you are seeing is entirely consistent with your user not being a service desk agent OR with the SD application simply not being active. But if you're in the global group (jira-servicedesk-user) and you are named as an agent in the Service Desk project, then you should be seeing all the SD…
-
Can you check who is an Agent in the roles in this project?
-
Queues belong to Service Desk projects, they can't pull from non-SD projects, because those projects don't have Service Desk data.
-
Have a look at https://confluence.atlassian.com/adminjiraserver074/managing-project-permissions-881683464.html The permission scheme contains: * Add Comments: Ability to comment on issues. * Delete All Comments: Ability to delete all comments made on issues. * Delete Own Comments: Ability to delete own comments made on…
-
Indeed, it's an off-the-shelf function already. See https://confluence.atlassian.com/adminjiraserver074/managing-project-permissions-881683464.html
-
When the assignee list is drawn up, JIRA looks at the permission scheme for the project. It only lists people who match the "can be assigned issues" rule in there. So, if you have a rule like "can be assigned issues: Role (developer)", then only people in that role will appear in the assignee list. You don't need…
-
Ok, so do you get all the service desk config stuff when you go into project adminstration for it?
-
Translations are handled by language packs, which are often incomplete, especially when Atlassian has no native speakers with the time to put into it. They encourage us to translate and contribute back into the language packs. I'm sure they would welcome your translations for the phrases that are missing.…
-
Ah, I'm guessing it's in the default user settings? The layout is something that applies across the whole of Confluence, so there won't be a space-based setting, it's by user.
-
The content of the assignee field is controlled with permissions. If your permission scheme says something like "Role: developers", then it will only list (and allow selection of) people in that role.
-
No problem, there's no harm in asking here, we can help walk you through all sorts of things. But the testing you've done on this one can only go so far - the next step is to look at logs, which is a support thing on Cloud.
-
There's no "switch over" option really, but you can get there. First, you can simply buy a new Cloud system, ignoring the one you've got by accident. Secondly, you can get a refund on Server - see https://confluence.atlassian.com/purchasing/does-atlassian-offer-refunds-321848767.html
-
It could be, but I would confirm that by reading the log first. If it is, then your database tools will be able to convert to the right collation.
-
We are end-users like yourself, so we can't really help you if we need to get into the stuff going on in the background. If you've deleted the page but cannot permanently delete it, then I suspect you'll need to go to https://support.atlassian.com/contact and raise it there for support to deal with.
-
I'm afraid not, we need the rest of the errors from Catalina.out
-
What does "not effected" mean? What happens when you click the button, and what do the logs say is happening?
-
I don't think it's possible - the anonymous user doesn't have a profile to save the setting to.
-
Two questions: 1. Why are you installing them separately? To get the best from JIRA + Software + Service Desk, you should be installing them as a single service - one JIRA, three applications, not two JIRAs with four applications 2. Which JIRA can't you open? The first one or second?
-
Ah, finding Eric in the assignee list would have got us to "case sensitive" after another step. Glad you got there faster though!
-
If you go to DOC-552 in plain JIRA, do you have the option to transition it into the status in the "done" column? (There's a good chance the status in Done is just "done", but it might not be) If there is no option to make it done, then you'll want your admin to look into the conditions on the workflow. If there is an…
-
Not natively. Events are fired no matter what, and notification schemes apply at a project level, not issue type. You'll need to find or write something that can catch events and send notifications on a selective basis, to replace the notification scheme.
-
Ok, can you test that they're assignable? Go to an issue in the project and click assign - is Eric a viable option there?