Comments
-
It's end-of-life for 6.4.all-of-them. You need to go to 7.anything to retain support.
-
Don't do it with SQL, there's all sorts of hassle and risks around doing it that way. I'd highly recommend either correcting your paths as Pawel suggests, or using the CLI as Bob said.
-
Hmm, well, that is a problem, but it's an issue as the server is shutting down - you need to concentrate on the upgrade errors.
-
Unless you have reconfigured it, you will find it under the "home directory" you set for confluence, beneath /logsShould be called atlassian-confluence.log
-
Yes, it means your upgrade has failed and you need to revert to the backup you took before you ran the upgrade. Preserve the log files before you roll back - you will want to read them to find out why the upgrade failed.
-
Yes, you can attach files to Confluence pages. There are loads of alternatives for documentation, but if you're using JIRA and Service Desk, Confluence is by far the best one to go with because it offers more integration than the alternatives (e.g. you can create Confluence pages directly from issues)
-
It used to be more open before Cloud, but people insisted on using silly settings and breaking stuff. They've never supported anything more open than ([A-Z][A-Z0-9]+) and on Cloud, it's all about being able to maintain large numbers of installations that all conform to standards.
-
I'd recommend you change that to ([A-Z][A-Z0-9]+) - there are plugins and features that go wrong when they encounter a project key that starts with a number.
-
It's not changeable on Cloud, one of the features they've disabled.
-
The 2 weeks clause is easy - it'll be "x < -14d", where x is the field you want to measure it against. (Updated?). You haven't defined what "survey" means here though, so we can't tell you anything for that. If it's a custom field then it'll be something like "survey = no" or "survey is empty", but that's just a guess that…
-
For the downloaded version, do nothing, the licence will expire. For OnDemand, see https://www.atlassian.com/licensing/ondemand
-
You'll need to clean the data. What's going wrong with the "altassian .jar" method? Can you confirm that you mean the Atlassian cleaner function? Have you checked what it's been doing with a "diff" between input and output?
-
Works fine for me when I go via the downloads page. I suspect it's the host redirecting you to a temporary url for some reason. Try it from the downloads page instead of a direct link.
-
He he. Happens to me all the time, there's so many things that could cause a vanishing issue (or set), it's hard to manage to check them all. I've got a particular blind-spot for the version filters on kanban boards...
-
Where are you looking for this? If it's filters, then this is probably the correct behaviour - filters look for issues, and if they're not finding them because the filter excludes closed issues, it's not going to pick up a sprint because none of the issues in the result set are in it. If it's in an Agile function…
-
The simple answer - install a temporary system of the version you're interested in and look at the "manage add-ons" page. Some of the default add-ons are considered to be "user installed" to separate them from "system addons", because you should not mess with the system add-ons unless you know precisely what you are doing,…
-
I thought that would be the case, but I didn't want to make assumptions!
-
When it arrives on OnDemand is up to Atlassian. I'm sure it's on the way though.
-
Atlassian will upgrade the plugin when they have tested it and are prepared to support it. You can't do anything about this. You might want to explain "seems not to be working" - a couple of our clients are using it OnDemand and it's working fine for them Although it might be worth raising a support request to poke them if…
-
You can. Could you explain the question a bit more please?
-
Off the shelf, most of those can not be done. * 5. describes a cascading-select list, I think With add-ons (free add-ons, and on cloud or Server) * 2 * 4 * 7 With paid add-ons, you can do the rest too, although I think you'll need several, unless you get the Script Runner (with Behaviours) which can do all of them, and…
-
Er, I think you've post this in error - there's no context for us to work with - no "snapshot" and we don't know what patch you're talking about?
-
That's a function of your network security, not JIRA. I'm afraid we can't really help you with that. JIRA simply serves up attachments or links when you click on them, it's not got any connection checking in it.
-
We gave you the answer. I'm not sure why you've asked the question again and then marked it correct when it's not an answer.
-
Agile is not available as an add-on for JIRA 7. You need to install the application JIRA Software. There are three routes you can take: * Install JIRA Core, then go to Admin -> Manage applications and add JIRA Software and JIRA Service Desk * Install JIRA Software, then go to Admin -> Manage applications and add JIRA…
-
No. See https://jira.atlassian.com/browse/JRA-1330 for the main discussion on this subject. It has a lot of suggestions, workarounds, and ideas that can help.
-
No. Jira's priority list is global, there's no support for schemes that would allow different defaults. See https://jira.atlassian.com/browse/JRA-3821 for hints and workarounds (and please vote!)
-
Apologies Colin, Angelica - I didn't suggest the direct route because I've tried it a few times and never had it work cleanly.
-
Ok, that's not a script, it's a database setting change - are you running that in the database? I don't know where that error is coming from, it seems to be unrelated to Jira. Maybe if you stepped through what you're doing and told us the handful of steps before you get to that point.
-
Script, no. But I would strongly recommend * Export the xml * Set up Jira 3.13, in a new empty database (i.e. leave the old one untouched, so you can always go back) * Import the xml into there (Jira will upgrade it) * Set up Jira 4.4.5 and point it at the 3.13 database Of course, do this in test first! That will tell you…