Comments
-
Um, the error is pretty clear. You've configured it to connect to LDAP to provide user information. The settings are incorrect, or it cannot reach the LDAP server.
-
That's what I was looking for - if that file is growing, then it's running an export. 3 hours is a very very slow export for only 42,000 issues though. What sort of system is your server? Memory, processor etc? Could you increase the size of the memory for the process?
-
Hmm. There are no errors there, and nothing I'd worry about in the list of plugins or the settings you have. What does the UI do when you visit it? Can you check the "export" directory to see if anything is created in there?
-
Then we need to go look at the full logs I'm afraid.
-
1. Spot on. The basic number you need when judging Jira's speed when it's doing an upgrade or full re-index is "number of issues in the jiraissue table". It's not a simple flat number because it is compounded by related data (e.g. a Jira with lots of custom fields will take longer than the same number of issues but no…
-
Technically, we probably need to know the size of your data and what your server speed is before we can tell you how long it should take to do any upgrade. However, three hours is probably too long. On a big fast server, I've recently done an upgrade from 4.0 to 5.1. It took 8 hours to do 420,000 issues. But, that time…
-
Because the data you are working from seems to be from version 3. That's what the log file implies. It does not say it explicitly, but the licence in your data is a version 3 licence, which will not work with version 4 or 5, and will not allow a version 4 service to run. You may well have a version 4.2.4 Jira running in…
-
Um, then I'm stuck. Your data REALLY looks like it's from version 3 and has not been upgraded to version 4. The licence in it is a version 3 licence. It refers to version 3 plugins. The errors you are seeing would not be reported if you were upgrading from 4.2 to 5.2, you would only get them if you are trying to upgrade…
-
Ok. Your Jira is showing distinct signs of being version 3.x, not 4.2. The format of the licences changed between version 3 and version 4. (v1 licences work for Jira 2 and Jira 3. v2 licences work for 4, 5 and 6). The licence error you're getting is because your data holds a version 3 licence. The cern email error you are…
-
These changed files should not be a problem. I assume you've changed jira-application.properties to meet your users needs, seraph-config.xml to talk to your user-authentication system, and web.xml for some network related onfig you need (if in doubt, then tell us what you've done to those three files). The missing files…
-
If you try to go over your licences, the systems effectively become read-only. But I don't think the user management system will let you go over!
-
Use the quisapps "field security" addon, or the script-runner/behaviour plugin (although that's not quite what it is intended for, and you will need some coding).
-
You're very close to an answer without any help. I think the bit you're missing is knowing how the pie charts break up large counts of data. When you've got large numbers, a pie chart becomes a bit fuzzy for very low counts, and because it's not very helpful to try to display a slice that's too small to see, the pie chart…
-
I'm sorry, but now you're just randomly quoting bits of the system without any explanation of whatever you are thinking. Please, look at the previous answers, work through what they say, and then post relevant questions, or you simply won't get any help. What you've just done here is a bit like: * Bhim: I need some help…
-
The name of your field doesn't matter, and what "code" are you looking for? Are you writing a plugin, external system or something else? Timothy's "code" above can simply be put into Jira's search and will return what you've asked to look for.
-
Ok, well, start at https://developer.atlassian.com/display/JIRADEV/JIRA+REST+APIs - there's a good introduction to using the Jira REST API, and examples, inlcuding stuff about fetching custom field data.
-
The whole point of using an issue tracker is that you can find your data. Start at https://confluence.atlassian.com/display/JIRA/Searching+for+Issues
-
It's you because you've got the project configured to default to assign to you, or the project lead (who is you), or the component lead (who is you). That itself can be changed quite easily - have a look at the prokect settings. To assign to the reporter, you need a post-function you can add to the create transition. I…
-
You don't really "add filters to boards" If you create a filter, you can create a board that uses it, but that's about it for saved filters. All the other filtering you do on boards is created and held as an attribute of that board - filters for colours, filters for swimlanes, quick-filters etc - these are not saved…
-
Ok, you need to be using JIRA Software (it's an application that is added to JIRA - check under Admin -> manage applications to see if you have it and to get it), and a later release.
-
That's built into JIRA Software
-
OnDemand has a fixed list of plugins you can install (via your atlassian account). You can't add ones that are not on the list. See https://confluence.atlassian.com/pages/viewpage.action?pageId=315326753
-
If you can't find it in the database, how do you know it's in there? Could you explain where you're getting the idea that there's a column? ex.(zeltech) means nothing to us, doesn't help us work out what you're talking about. Could you tell us what you're seeing on a Jira screen and where?
-
Ah, ok, it's just the wording of the message.I'm afraid that is buried in the core code and I suspect it's in the java rather than a template, so you'd have to recompile the class throwing the error message. If it is a template, then that's a little easier, because they're simple text and you can just change them in the…
-
You should not get rid of the message, it is telling the user why they cannot create the issue. If you want to let them create the issue without that field, then go into the field configuration and make the field optional.
-
Ah, I see, the outgoing mails have the wrong email address on for the email clients to pick up "reply to" on them. I've run into this once before, but not worked out a decent fix for it I'm afraid.
-
Sounds like you need to configure jira to "create or comment" by email
-
Click admin, and search for "backup".
-
Select type options in Jira are lists of options, there's no hidden values behind them for you to set. I suspect your only option here is to literally have 1, 2, 3, 4, 5 as options and then have your calculation code start with something like "value = parseInt (getCustomFieldValue(cf).getValue() )"
-
I would raise this directly with Atlassian. When I last asked, it was a definite goal for the team, but I don't know what's on their roadmap for it.