Comments
-
The command I gave you (ps -ef | grep -i my) clearly states that there are no processes with "mysql" in their name/description running. MySQL server almost always runs at least one process with mysqld in the name of it, unless you've deliberately hacked it to run with a totally different name. The service script is…
-
Er, well, that's a dead giveaway >MySQL is not running. You can't connect to a service that isn't running. Because it isn't running. You need to start MySQL and retest.
-
Oops. I forgot. Can you check that MySQL is actually running? You get that error a lot when it's not running. Try "ps -ef | grep -i my" Possibly, but I'm not sure. Could you also try mysql -h 127.0.0.1 -u user -p And mysql -h ::1 -u user -p And check the error messages carefully. (Your Jira config looks absolutely fine,…
-
Usually means mysql isn't running. Try logging into the database using the mysql client tools to verify that.
-
Short answer - remove the resolution field from your edit screen. It's wrong. You've done nothing wrong with status or transitions, it's just resolution. If you put the Resolution field on any edit screen (create, edit or transition), then it will be set when the user commits their change. Doesn't matter if they don't…
-
It's more likely to be a browser or even network issue. I can replicate it by logging into a Jira, then temporarily disconnecting the network, or clearing my browser cache - the main JIRA display stays there, but clicking on the menu gives me nothing. (I'm not saying these are the only causes, just that I've seen it do…
-
Click "create"?
-
Never any harm in asking - at a glance, the documentation doesn't explicitly say it (Although I'm sure it's there somewhere).
-
Control panel -> Software -> uninstall
-
No, you're missing the point. There is no "alternate solution" on the file names other than "use Jira as it is intended". Your expectations are incorrect and you are NOT going to get this changed. The only way to change this behaviour is to hack Jira core code, which is a really bad idea. This, of course, leads to the…
-
There is no "resolution". Jira is storing files you attach in the way it's designed to. You aren't going to get the same file names on the file system. There are only two uses designed/intended for the attachments in Jira - Jira uses them, and you should back them up. You are not expected to use them in any other way.
-
You're probably doing it wrong then. Where have you diverged from the instructions?
-
You can't really "size" the effort involved without referring to the complexity of what you're going to do. If you're going to use the applications pretty much off-the-shelf and not fiddle around with themes, non-atlassian integrations, workflows, addons, fields, and and and, then the maintenance is quite low - you'll need…
-
Because your workflow has two reopen transistions in it and you match the condtions for both of them, so you could use either. Talk to whoever built your workflow - they've probably made a mistake.
-
In its current form - never. It's a server add-on and Atlassian are not only not accepting new ones for consideration, they're trying to get rid of the current Server add-ons they do offer. If the vendor were to write a Connect version, that could go onto Cloud, but it'll be quite different to the current functions you get…
-
I don't think you're alone - the last update has been a disaster for a lot of users. I'd add a voice to https://answers.atlassian.com/questions/36182163 as the main one.
-
Sorry I didn't get the right answer yesterday. I'm going to blame a bad memory and bad coffee.
-
Oh, hang on, I'm really sorry, I've made a mistake. I forgot that the sharepoint connector is a bundle, NOT a plugin. What you need to do is take the download .zip file and unpack it. You'll find it contains directories with assorted files in them - you need to try installing the plugins from the "confluence plugins"…
-
My guess is that you've downloaded the Confluence plugins using Internet Explorer and you've run into the bug that it stupidly and pointlessly renames some files when you download them. You could try downloading with a proper browser, or try renaming the .zip to the .jar file it should be
-
When you deleted the space, you inadvertently killed off the space permission that said "let anyone in". I can't tell what it was before, so you need to do one of these two: Go to space admin -> permissions and re-add the groups you were letting in before (confluence-users?) Go to space admin -> permissions and look for…
-
What tree?
-
What is the error they get in the browser?
-
Not quite the same way, but it does use REST. It has an add-on component that allows for more calls than plain REST allows.
-
The REST API does not have the administrative functions for updating fields, like JIM does. To use REST to do this, you've got to have all the supporting data in place before you can import.
-
Ok, then your WAF has a rule that is wrong. In both cases, it's saying "cross-site script check" failed. You'll need to get the WAF administrators to explain that rule and then get them to fix it so that it does not get triggered by Jira. The reason I say that is that there are no cross-site attack vectors in either of…
-
Good. I can't see any way of fixing this without them telling you what your WAF is blocking and why it thinks it should block it. Once you know that, then you should be able to tell them what they've got wrong...
-
I have to agree with Radu here - it is irrelevant what your WAF administrators are telling you. They need to EXPLAIN what content is "wrong" and why. Then you need to explain to them why you are posting it and why it is safe. Then you need to get them to change the settings on the WAF to accept it as valid. I cannot…
-
I'm sorry, I don't understand that. I understand that you're telling us that the WAF is set at low level security. I do not understand the "post open source content on the request" part. However, I really do not think Jira, or even what you are posting is a problem. The situation appears to be that your WAF is blocking…
-
That is still your security software interfering with the requests. If Jira is working internally, then that is firm proof that the security software needs configuring to allow external access properly. It's nothing to do with Jira and Jira can't be expected to do anything to fix this - it's the WAF that needs…
-
Putting a link in a summary so we can't even click or copy and paste it is REALLY unhelpful