Comments
-
That should work fine, but I can't remember if the server ID will change. If it does, then you'll need to re-generate your licence key. But that's it, your licence is valid to run one Production copy of Jira, and it doesn't care about versions (unless it's expired and you want to move to a version released after it expired)
-
If the UPM is not suggesting an update then you shouldn't do one. Whatever version of the plugin you are thinking of trying to install is not compatible with your Jira. Forget it, it's not worth the bother. Yes, I'd copy the database with native tools. The data won't actually change if you stay with precisely the same…
-
1. Yes 2. Don't - it's part of the system and you don't want to mess around removing it. Check the UPM for updates, and if that doesn't say anything, leave it well alone 3. Probably not. Java memory tuning is not that simple. You probably don't have enough memory to run it a 2Gb - read the log to find out what's going on…
-
Admin -> Services and delete the backup service (you can always add it back if you change your mind)
-
That's rather old code I'm afraid - if you look at the pom.xml, you'll see it says "jira version 4.1" near the end, and that's from before Atlassian swapped osuser for crowd. However, that should actually make it compile for 4.1, so I assume you've already changed it to 5.0 You might be better off using example code from…
-
Your code refers to stuff that changed in Jira 4.3, you need to update it with the new API calls to do what you need. I'm assuming you've got a plugin or code for Jira 4.2 or below and are trying to update it?
-
Depends on how you've set it up, but there is not enough information here to be sure what you are seeing and what is wrong. The most likely scenario is that you have customised screens, set up so that issue-CREATE includes the field, but issue-EDIT (and possibly some or all of your workflow transition screens) do NOT…
-
I suspect your users do not have "browse users" permission. Go into Admin -> Global permissions and look for the browse users permission - you probably need to add "jira users" to it.
-
Short answer - don't. Long answer - Rewrite a whole swathe of the core functionality. The resolution field is embedded deep into the structure of the system. It's used as the baseline "is this issue open or closed" question, and excising it means removing that and assuming all issues are always open, or replacing it with…
-
If it's deactivated in your OnDemand account, you won't get charged. The reminder may be telling you that you have not correctly deactivated it though. However, we can't help you - we're a community of end-users like yourself, we are not Atlassian support. You should get in touch with Atlassian OnDemand support to make…
-
You can't. See https://jira.atlassian.com/browse/CLOUD-5685 for the request to allow you to do it.
-
This is the fourth time you've asked this question and you've ignored John's answer. See https://answers.atlassian.com/questions/210452/redirect-the-existing-on-demand-confluence-uri
-
What "access" do you want to restrict, and what do you mean by "sex roles"?
-
You don't need to do anything - if your licence for JIRA has not expired, you're entitled to use 4.2 and 7.1 and all versions in between with it. For JIRA Agile, you need to move to JIRA Software (your Agile licence should work for Software too)
-
I'm afraid so.
-
They have to be identical. In the screenshot you've given, you would need to have Bug and Feature using the same workflow.
-
You get no access to the servers running Cloud installations, and certainly not the code running on them. So, no.
-
Heh, yes, I saw it, didn't think it was worth deleting to be honest, it looked fine, albeit not quite Atlassian any more. My thought was "that's just what I chose to do because DietPi keeps it simple and single-purpose which is what I wanted for some boxes. I go to Raspian for any general-purpose ones. I'd recommend using…
-
Yes. H2 is a better in-memory solution than hsql, but it's still got the same flaws because of the very nature of what it's doing. For what it's worth, I've got a test rig here that works fine for small usage: Pi 2: running PostGres Pi 3: running JIRA 7.2 Both with external usb drives. Both built with DietPi and not…
-
Catastrophic failure is the short answer. It's rare (and even more rare than the failures we've seen with the old HSQL option for JIRA 6 and below), but can still happen, and, like HSQL, if it does go, it's very unlikely you'll be able to recover it without resorting to backups. It's hard to say it would change…
-
Nope. Sorry, our comment's timings crossed over. See the other thread ;-)
-
No.As I said, the licence does NOT care about the version. If you have a licence, you can use ANY version of Jira from 4.0 to the last version released before the end of your licence. If you bought a licence today, you can use it with 4.0, 5.2, 6.4 and any later version released before March 24th 2016.
-
The licences don't care about your version of JIRA. If you buy a licence for 6.4, it will work for all versions back to 4.0 (the licence file format changed in 4, so if you want to go back further you have to get an old-style licence)
-
Ok, I'm not sure how to fix it either. I've run into something similar in my add-ons a couple of times, and fixed it mostly by trial and error - removing imports that it refers to so that it's only trying to us a single library, but I don't think that's a "good" approach (it shouldn't be!)
-
You'll need to contact the vendors of the add-on. It's not compatible with JIRA 7 and needs updating and recompiling. I'd go to https://marketplace.atlassian.com/plugins/za.co.infowarestudios.jiraplugins.infoware-quote-plugin/server/support and try the linked issue tracker to see if you can raise it there.
-
Check that the permissions on the driver file you have installed are correct, and that the file belongs to the same user as the other files in there. That's the bit I forget to do every time.
-
It means your JIRA server can't reach the marketplace for some reason - I can reach it, so it's probably a network issue on your side. To bypass the need for a connection, go to the marketplace in a browser, find your add-on, download the right version and then use the "upload add-on" function in the add-on management page.
-
A long time ago, there was a move to do some version heirarchy, but I think it was dropped when Greenhopper was widely adopted (that became Agile and is now Software)
-
There is no way to do that - you've got separate values in the field, so JIRA reports on them separately. If you were to find/write a custom report to look at your JQL, you could do that sort of thing.
-
Duplicate of https://answers.atlassian.com/questions/56487353