Comments
-
It's historical You should not be reading the database. That way lies terrible code and a broken JIRA
-
The site responds to me, but I obviously don't have a login. What does "can't contact customer support for some reason" mean? https://support.atlassian.com is working fine too.
-
Er, no, they've explicitly stated that Tomcat is the only application server they can officially support and dropped all the others as of Jira 4.2. There is no harm in asking though - they WILL try to help you, even though they may well end up with "move it to Tomcat and try again" if they are stuck. See…
-
Supported, no, Atlassian only support it on Tomcat. It is possible though - I've recently seen it running fine on Weblogic 10.something. I'm not sure I can help you with it, as it wasn't my setup and I'm not in touch with the chap who built it.
-
The screen layout is not important - the CSV imports data into fields, it's got nothing to do with how they are displayed.
-
That still doesn't tell us whether you have mapped ImpactInBusiness many times? Just to make it entirely clear, could you rename the columns in the CSV as (say) ImpactInBusiness_1, ImpactInBusiness_2, ImpactInBusiness_3 and so on. Also, I apologise, I was not entirely clear when I was talking about "mapping". There's two…
-
That project is not public - we can't see stuff you raise in there. I've just tried to run your file into a test system, it's working fine for me.
-
Can you make sure you are selecting the same Jira field for each of the impact fields in the CSV? It should be asking you about each column separately.
-
Are you mapping the incoming data? Can you try moving all the nulls to the end of each line?
-
Right. That is covered in the documentation, as usual. Read http://confluence.atlassian.com/display/JIRA/Importing+Data+From+CSV and pay close attention to the section "valid file format", which tells you how to import multiple values into a multi-select field.
-
I'm sorry, that makes no sense what so ever. When importing into a custom field, you tell Jira which column in your CSV contains the data, and if it's a select field, you map the options (Check boxes are a form of select list by the way - the difference is in the way they are displayed, not the actual data structures). I…
-
Yes, you can do estimates in Jira.
-
Ah, good, I did understand it correctly then! Thanks! Boris has beaten me to all the links I'd recommend. The only thing I'd add is that you should stop thinking about doing things at a database level (forget triggers and keys etc) - you need to use the functions for handling AO as documented in Boris' links.
-
You can't use the database in Connect either, so I'm not sure what you're doing. I'd assumed you were reading an external database and your addon will continue to do that.
-
Yes, as long as it's not the JIRA database - you must never write to a JIRA database directly.
-
You're pretty much stuck. I'd strongly recommend getting your users together and talking them through using a standard scheme. Your other option is to stop using the internal priority field and use a custom field instead, but you'll lose all the built-in priority reporting.
-
I think the thing you're missing is, well, a version for Linux. There are only versions for Mac and Windows. You could try running it under Wine, but it fails terribly when I've tried it. There are emulators you could try too, but if Wine fails, I generally don't hold out much hope for emulators.
-
You need to explain what you're trying to do before we can answer that
-
You've got a broken "scripted field". The trace does not contain any information that leads us back to the field that has your broken script. You need to look at all your scripted fields and work out which one is broken and fix it. I'm afraid you need to work your way through the scripted fields one at a time.
-
Good, I was hoping you were in test. I've said "use the UI", but what I really mean is "use the API" - your database approach is poor and broken (there really should be a banner across every Atlassian site saying "don't touch the database"), but the UI sits on top of an API which is safe to use. The API is also accessible…
-
Do not make changes to an Atlassian application's database. You need to know exactly what you are doing (depending on the version, you've started in the right place, but I suspect, missed things), and you should always have the system offline, and backed-up with a proven restoration before you attempt it. You might want to…
-
You can't go above UPM 1.1.4 with Jira 4.1. All the UPM versions higher than 1.1.4 are incompatible.
-
Talk to sales@Atlassian.com about this. Generally though, yes, you can let the license lapse (you won't lose any functionality) and then re-purchase later. This will be treated as a new license though, and not a "renewal", so it may not be worth it. Atlassian will be able to explain exactly what will happen in terms of…
-
Saurabh, you're asking very similar questions in several different ways without waiting for an answer. This is not a good way to ask questions in a forum, you end up ignored or with scattered and unfocussed answers. See https://answers.atlassian.com/questions/180246/in-confluence-how-to-create-own-java-and-vm-velocity-file
-
Well, there is, but it's not ready for us yet. It will be released when it's ready (Atlassian don't do dates, they release when they think the software is ready for it)
-
Change the board to use the time as the estimation statistic
-
You should be able to use a post-function that can check for an existing directory in a system and create a new one if it's missing. You'll need to write some code for it. I would, as usual, use the Script Runner to do it.
-
Not really, you need to associate them because Field Configuration does one thing, and Field Contexts do another. You can only get fields included in projects automatically by making them global.
-
Is the "closed" status in the far right-hand column on the board?
-
Yes, get them to remove the theme, or adjust it for better contrast.