Comments
-
JIRA is database agnostic - it uses a database driver to talk to the database, but it has no understanding of what the database is behind that. If you suspect fragmentation or database indexing to be issues, then you need to deal with them on a database level.
-
Actually, Joe said JIRA home, not JAVA. But yes, that's the right thing to do with JAVA_HOME, and your point about Solaris picking up odd versions is definitely the next thing to check! However, I've just noticed Joe said he put JIRA_HOME into server.xml - that's not right - it needs to be in jira-application.properties,…
-
You might want to try Java 1.6 - it's not supported below 1.6 That doesn't mean that it won't work, just that if you do have a problem, Atlassian won't feel obliged to help you and their first suggestion will be to try 1.6 and see if you get the same message! See…
-
Possibly. But it's easier to explain what should be happening here: * JIRA Core is a full service which acts as a server application providing the Core functions of JIRA, AND a framework for other JIRA Applications to run on. You install it on it's own on a physical or virtual server. * JIRA Software is a JIRA Application…
-
Have a look at the board filter first, then go view it in the issue navigator. At the top of that display, there are export options. These used to include "excel", but that's been deprecated and you're expected to use CSV exports now (you can re-enable excel in current versions of JIRA Server with a flag, but I don't know…
-
Nothing to stop you entering a username or "Raymond throatwobbler Morgan" instead of a real name.And it doesn't matter if you're a small organisation if you're in a field that is regulated (it's illegal to not use identifiable names in finance for example - doesn't matter where you are, who you are or you have 1 employee…
-
You'll need to amend quite a lot of core code in Confluence to do that - users prefer the use of their real name, and it's a lot more sociable and friendly to use a display name, so Confluence does this correctly and allows a display name.
-
Have you tried resetting the password for atlassian.com ? https://support.atlassian.com is the place to rise this - it sounds like there is something wrong with your accounts and they've been disabled. If you cannot login there even after a password reset, I'd create a new account to enable this to be done.
-
A page title can't be html - you can't use html in links. As for your suggested html, well, it's already there when you view a page. A bit more complex, but it is there.
-
No, they're numerical because it works with numbers. Best you can do is agree with your users what number a shirt-size should be. Or use a custom field for it first, and use story points for more accurate numbers afterwards
-
This has the feel of a question in the wrong place, but I'm not sure. Could you explain which Atlassian product it is? Although to pre-empt it a bit - the use of the word "ticket" implies you are looking for an issue tracker, which is Atlassian's founding product... So look up "JIRA REST API" in the documentation
-
Your production installation will be absolutely fine. Your best option on the test instance is to use the development licence on it instead (you can get this from the licence page on your my.atlassian account). It's intended for dev/test and failover systems.
-
Ok, you'll definitely need to raise that with Atlassian's OnDemand support.
-
Probably - you're trying to run arbitrary SQL, and I think Atlassian are trying to get at the same question I asked, and you didn't answer - "What are you trying to do"? What's the report, the requirement? What are you looking for? What's the question you are trying to answer here?
-
You've said you're on OnDemand, so you can't install plugins and you can't access the database directly. However, if you were running your own installation, then you could use some SQL, but your question isn't really clear enough to give you an answer. Anything can run SQL against a Jira database, you'd use whatever tools…
-
Neither of those are fields in a standard JIRA database, so it looks like you've done something to add them I think you're going to need to explain where they have come from first!
-
I'm not sure you can, but I will have a look presently. You can stop them with a simple workaround - give them a workflow that is used by another project. You can only edit a workflow if you are the only project using it. I suspect that's going to do most of the job for you initially, if you're centralising shared…
-
No, there's no search-and-replace function, or a plugin that I know of that will provide it. If it were a handful of issues, I'd suggest resorting to manual edits, but for a larger number, I'd look at scripting (via the Jira CLI probably), writing a quick "bug-fix" plugin, export-edit-import the xml or possibly an SQL…
-
Ok. Have you got a v4 licence for Jira at all? If you have, can you try logging into your my.atlassian account and see if you have the option to downgrade next to the licence key? If you don't, then I'm afraid you are going to be pretty stuck - even if you had a licence in the past, you can't upgrade to any version…
-
The problem here is that the recommended upgrade path from 3.x to 4.x is to export the xml and import it into version 4, and to do that, Andrey needs a licence. If you have a valid licence, you used to be able to swap between the v3 and v4 formats, but I've not had to do that for ages, so I do not know if Atlassian have…
-
I'm sorry, the filter is irrelevant - you can't have an empty summary, so all it tells us is that you haven't broken it by database hacking. The problem remains that it thinks there is at least one line in your CSV that does not have anything for the summary.
-
Your CSV is missing at least one summary. Have a look in the "summary" column - you will find that there is at least one line with no entry
-
There is also reporter-browse which lets you set up a project where a user can only see issues they raised themselves, but if your customers have multiple accounts, it's not that much help.Yes, the second option is to have one project per customer.And the third is to use security levels - these let you say "when security…
-
I'm afraid that won't work for separating out the customers
-
Yes, but you'll probably need to revise your permissions and groups. JIRA ships with a default group "JIRA users", which is used to say "people can log in". Unfortunately, it is also used in all the defaults to say "can use project", which means you end up with a completely open JIRA where everyone can see everything. You…
-
I'm sorry, that doesn't make any sense - "I want that only a specific group of people should be able only comment field in jira" is missing a verb - what do you want this group to be able to do? View the field? Edit it? Enter data in it?
-
That's exactly where I was heading in my follow up answer.
-
How are you telling JIRA that something is blocking an issue?
-
First, define a filter that matches the issues to email people about, save it and share it. Now, you need to decide between * Getting people (or a dummy user -> mailing list) to "subscribe" to a regular list of all matching issues ( http://confluence.atlassian.com/display/JIRA/Receiving+Search+Results+via+Email ) * Using a…
-
No, everyone sees the fill list for the project. You can play tricks and prevent people from raising certain types, but if you want to restrict the list on creation, you'll need some coding. I think the behaviours plugin used to be able to do this, but can't vouch for version 5, and I've seen some attempts to use…