Comments
-
It's not just "when no one is using it" - you really should take Jira down while runing database changes. It caches some things in memory which it will happily write back to the database and wipe out your changes. So don't run SQL while Jira is running.
-
JIRA Software is an application that runs on a JIRA Core platform. (I'm being fussy about wording because "add-on" is a different thing to an application. Despite the fact that they are both things you add to JIRA Core) A JIRA Software download includes Core because it is needed to run Software on top of. And, of course,…
-
Er, javascript is a totally different thing to java. You'll need to read your browser's manual to find out. I don't know what you're using. Most browsers default to having it enabled, but a lot of security conscious people block it for good reasons, only allowing it when it's genuinely needed.
-
No. You need a browser, but not java. Some older versions do ask for java, if you want to use the "screenshot" function, but that's the only thing you need an install for.
-
It doesn't. Well, none of my installations do it. I go to JIRA in a browser, no JRE installed on a machine, it works. What, exactly, are you doing here?
-
No, they don't require it. JIRA does have a "screenshot" application that relies on Java, but it is usable without it and you can still attach files without it
-
I'm afraid that is, as I feared, the wrong answer. You should not lock the table, you need to correct the settings on the server side. Jozef already dug that up for you :-)
-
Why do you think you need to lock the tables? It's pointless if things are working properly, which suggests you're breaking something, or you've got an issue and you're reaching for some solution (and in this case, you're reaching for the wrong one)
-
No, it won't appear until you have got data in it. JIRA hides empty fields in an attempt to reduce screen clutter.
-
It pretty much depends on what exactly you mean by "change control"?
-
It's been raised a few times, Atlassian have closed them as "won't do"
-
There's no way to turn it off - Atlassian believe it's far too useful. You'll need to start messing with the core code, or javascript hacks to disable it.
-
Atlassian use curl as an example because it's quite simple to use and installed on a lot of machines automatically (and even when it's not, it's usually very easy to add). It's good for examples because you can concentrate on the content, and not how a program is working. > i need to change the default js files for my…
-
Absolutely - use JIRA's REST API to poke the data in - see https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-create-issue You can do it any language that can produce REST calls, so the next question is "is there a way your 3rd party app can be made to make such a…
-
Yup 1. Create a role for developers, put each user into it, and amend the permission scheme for the project to say "browse = role: developers" 2. You might want to have a way to identify customers, but on the assumption that you want anyone able to create issues (not see them initially, just create), I'm just going to use…
-
That's a lot more simple. I think the table you need is cwd_membership. If you're going to execute SQL updates of any kind on a Jira system, then the procedure is: * Stop Jira * Take a backup of the database * Prove the backup works by restoring it to a test system * Run the SQL * Restart Jira * Normally, you'll need to…
-
SQL is still a really bad way to approach this and it's pretty certain that you'll break something, unless you spend weeks getting your scripts exactly right. You must already have the list of users to remove if you were thinking of using SQL, so you should take that and convert it to Jelly (this is easy with a spreadsheet…
-
Er, don't. If you try to remove them with SQL, you'll need Jira offline while it's running, a re-index afterwards, you're open ot unexpected problems and data corruption, and you will have to back up properly and test the backup before you do this. On the SQL side, I can name 8 tables you'll need to worry about (2 of which…
-
Oddly, there's some documentation on it - https://confluence.atlassian.com/display/JIRA/Creating+a+Notification+Scheme
-
Have a look at the notification schemes - you have a lot of options there, over and above "watcher"
-
In which Atlassian product?
-
Have you found (or asked for) a fix for this problem on https://jira.atlassian.com/browse/JRA ? The prioritisation of issues in there may not work for us end-users, and there are (big, sweeping) changes Atlassian develop that do not show up in the list, but unless this is logged there, it's not going to get done. If it is…
-
Your mysql server is configured to refuse connections from the JIRA server. You'll need to go over the server settings on the database side and reconfigure it to allow connections.
-
There are some fields that can be mandatory as Confluence is going to pass them in anyway. Summary is the obvious one. You should be able to read the error messages to see what the call is failing on.
-
Ok, yes, that confirms my assumption. You'll need to make linked issues optional.
-
Probably. You have not really described why you "can't create" - no error message or description But I think I can guess. The Confluence create routine relies on sending basic details to a JIRA system. It has to assume a standard set up. But, I suspect you have made the project in JIRA require more than the standard…
-
Same as the other parameters - add something like the below (obviously, replace my random strings with your server url and your admin password) --server "https://yourconfluence.somethingrandom.com" --password "RandomPenguin"
-
I think there might be some context missing from this question, but I'll take a stab at an answer based on a guess at what you're doing. As an administrator, add the custom fields to the "screen" that is used for "create issue" in the project. Then you'll be able to add data to the issue as you create it. Later, if you…
-
Get rid of the add-on causing the problem. You might want to check the logs further to see if they can tell you what the root cause is.
-
It looks like you've got an add-on that's trying to inject some library that's already in JIRA and they're clashing because of it.