Comments
-
No, there's no installer, they're more recent packaging. The unpacked files are fine - you need to edit the properties file to set the home directory, then just go into the "bin" directory to run the start.sh
-
Same key should work for 3 through to 6 if memory serves.
-
https://www.atlassian.com/software/confluence/download-archives/
-
Ah, and yes, upgrade to 5.8. If you want to go to 5.9, you need to test that path properly before doing it.
-
Ok, so if you tested an eval version, you already know where to download it.Have you completed the testing of that and proved it all works? If your upgrade test went fine, then you should follow the same process to upgrade production - go to 3.5.17, then whatever other versions you went through.
-
The simple answers are: * No, you need to upgrade to 3.5.17, then you can think about 5.x * Go to the downloads page. Click the download link on the versions you need to step through * My guess is that you mean Bob's rather excellent HTML addon, which will work with 5.9 and should be installed via the plugin manager…
-
Probably. If your default says "allow access to everyone", then yes, you'll need it to stop doing that. Or, stop using the default, and create your own.
-
Change the permissions so that the default is to allow no-one access, then build up the permissions for your other projects to allow your other users, and that project to allow that user. It's all at https://confluence.atlassian.com/display/JIRA/Managing+Project+Permission
-
Your first question is answered by itself I think - use conditions to prevent people going to the wrong status. The second is a bit more of a "no". A transition in a workflow always uses the same screen, so your options are limited to: 1. As you suspect, two independent workflows 2. Use conditions. Create two parallel…
-
Yes, it's only for webwork actions, although a lot of Jira is controlled that way. It is definitely *not* available in OnDemand.
-
Administrators could still disable/remove the plugin. I don't think there's any answer other than "You have to trust your administrators". I suspect that applies to all software, there's always a way for "root" to do something.
-
Yup, you can say "assignee is empty"
-
A quick clarification - when you say you're going from 3.5.16 to 5.1.1 (or 5.3.4), is there a reason you've skipped the recommended route of 3.5.16 -> 3.5.17 -> 5.0.2 -> 5.higher?Actually, I've found 3.5.15 or higher -> 5.0.2 works fine, so I'm not worried about that. But I've had exactly the same symptoms you have doing…
-
No. Of that list, only "thumbnails" is totally safe.There's a lot of data in the other three directories which is ok to lose or delete, but it has consequences. Deletion of plugins-osgi-cache and temp means longer startup times and potentially some odd behaviour in places (nothing fatal, but you might get complaints).But…
-
Not quite sure what you're looking for here, but if you are asking just about re-indexing, then you'll find that the caches directory is heavily affected and the rest of it is untouched (beyond adding to the logs)
-
No, there is no API for that yet.
-
For JIRA, see https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html (there's no need to worry about your agents on top of your normal users - think of them as users who do some different stuff but don't add more or less load than a normal user) For Confluence,…
-
There's quite a few things that can end up with this error. Giving the wrong password in some cases, but the main ones are a corrupted key file, a damaged keystore file, very unusual characters in something in the keystore (password or filename) and I've got a feeling there are more. You need to start by looking at the…
-
Actually, no, a multiCore CPU is not an absolute requirement. It's good to have if you can, but even the latest version of JIRA can be persuaded to run fine on a single core.The problem here is the memory. I would never try to run a multi-user Jira in less than 512Mb RAM, and even for low-usage ones, I reach for 1Gb as a…
-
Should be, if you pick one that has enough resources to run it (it can be a bit heavy on a server, and a lot of the lower-end virtual servers available aren't quite good enough - look for a minimum of 1Gb memory) You'll need to be able to log in to the server on the command line, and upload the installation files. Ideally,…
-
I assume when you say you accidentally launched 6.3, it was pointed at the 6.2 database? That means you're pretty much stuck. 6.3 will have upgraded the data to 6.3, which makes it useless to 6.2. Your 6.2 install is now detect the version mismatch, thinking "it's older, I should upgrade" and falling over because it can't.…
-
You don't. You can set the space to "anonymous access" and anyone will be able to read it without logging in. Or, you could create a dummy user with a shared username and password.
-
Sorry, I'm still lost. If it's doing the CRUD for you, what's the problem? If you need to "hard code" a value, then set it in your code, just don't ask the user for it.
-
Now I'm completely lost. You say it's handling it automatically, so there's no problem. So what is the actual question?
-
You'll need to explain what the Restful table is for most of us. Although from what I've read (assuming you're using the one google points to) it should handle it automatically. I think you also need to explain where you are stuck
-
Oops, sorry, I forgot. You could also put this into the workflow, without code. Create a transition from a status that loops back to the same status. Give it a transition screen. Place your customfield (and nothing else) on that transition screen. Then you'll get the same effects.
-
You'll need to write that as separate code, but yes you can do that. Bear in mind that it will still do what "edit" does. You'll have those two fields on screen. Custom-field will be *changed* by your user, and the comment they put in *added* to the end of the comments list.
-
Absolutely, although it's the other way around - you update the field value in an edit screen and you will be offered a comment box.
-
No, customfields belong to issues, not comments. You could move things around in the comments, including a customfield, but that would not stop the custom field being an issue item.
-
Please could you have a look at the link I gave already?