Comments
-
My guess is that you're on Cloud? Where you can't set up new mail servers, as it's a restricted function (and there's already one configured and running for you)
-
You can't do it without hacking the code behind the links, and even if you do that, you're going to have to be very careful and think through exactly when it should open a window and when it should not (that would be almost all of the time...) I'm afraid John's suggestion of "let the user decide when they need a new window…
-
NB is widely used in English documentation, it's not non-standard. (A faintly archaic notation I'd say, but I like it, it goes well with my over-use of i.e. and e.g.)
-
Yes, see https://jira.atlassian.com and check for similar requests before you raise a new one. However, you should check the marketplace for add-ons that might help (I've not seen one for this, but there are so many add-ons, there's a good chance I've missed one).
-
No, there's no functionality for that in JIRA.
-
There could be any number of reasons it stops. Sometimes, yes, a human does it, sometimes it's resources, sometimes it's a bug, and so-on. Start by reading the application log - look for the last time it restarted and then read backwards from there. Are there shutdown messages? "I am struggling with" type warnings or…
-
Click edit. Change the dates. Or just click on the dates in the issue view to use inline edit. I think there's a more complex question here, but you have not explained what you mean by evaluated or approved, how they apply to issues, or what you have configured that may be stopping your edits.
-
Nope, it's not. Core doesn't have a project pivot report. I suspect you're using an add-on, but I can't be sure which one, because there's a number that mention pivot reports.Do you mean the Timesheet one that @Ignacio Pulgar suggests?
-
You'll need to explain the "project pivot report" bit. What is the filter behind that, and what does it return? Then, what do we see in excel?
-
Every page you edit is a new version, and there's a full history of every change (unless you deliberately delete) Every attachment you upload gets a version too, as long as the file name is the same. It's simple versioning (no branching or other clever structures, just file v1, v2, v3 etc), but it's all you need for…
-
I think you'll need to expand on that a bit, to get a useful answer.
-
That's the sort of error that happens when you have encoding errors earlier on. If you have fixed the encoding error, then your log should be cleaner - could you show us the ne wlog you get after having fixed the encoding?
-
Look at the first error in your log - it tells you exactly what you have missed when you set up the empty database.
-
No. Filters are nothing to do with projects, that's why they weren't imported. The most simple way is to manually recreate the ones you consider essential. There's no real way to transfer them between instances.
-
No. That's a vast oversimplification, and not helpful at all. You absolutely should upgrade if you want to reduce the problem. In Atlassian applications (like most others) stack traces only go to users when the application is not coded to catch them properly and present something nicer. Upgrading will reduce the frequency…
-
You don't. It's designed, like all good systems, to tell you what is going wrong.
-
I think we were typing at the same time :-)
-
I think that was an answer to my question, not yours about the log. Useful to know, but my follow up questions to that were going to be "do you get the error when looking at an individual issue", and then... "what does your log file say"?
-
When is this happening? I'm afraid "while checking summary" does not tell us where you are or what you're doing.
-
That would make sense - the "" in the issueFieldMatch means "read every issue in JIRA" - that's going to be a disaster in terms of performance in any medium to large JIRA installation.
-
Script-runner itself will not cause memory errors (unless you've got too little memory to load it in the first place, but that would apply with any addon). It's what you do with it that matters. You'll need to take a close look at the query that your users are triggering to work out what it is doing here.
-
Ah, attachments, yes. You'll need to edit the main page directly. Copying and pasting text should still preserve headings for the TOC though, so you should be able to do blocks of rendered text to replace the includes.
-
I'm afraid there's no easy way to do that. You could start messing around with scripts or exporting pages and re-importing them, but the best option might be a simple copy and paste exercise. If you want rid of all or almost all of the includes, there might be some mileage in copying the whole page as it is rendered and…
-
Download is a bit more complex. You pay what they say up front on that page for the first year. Renewals are then half that, every year. Same rules about scaling and changing the numbers of users apply though.
-
It's covered at http://www.atlassian.com/software/jira/pricing Basically, if you move from one band to another, you pay the difference. Eg. you've got 30 users, you're in the $2,200 band. Doubling in size to 60 users moves you into the $4,000 band so you need to pay $1,800 on top of your initial $2,200. If you do this…
-
You can do it, but don't. If you have duplicate email addresses, then JIRA cannot uniquely identify a user. If you have any form of incoming email processing (creating issues or support requests, or even commenting on issues), then it will fail because JIRA does not know which user to use. There are some other problems…
-
You probably need to explain what the "CMS Water Cooler" site is. A Cloud based Confluence?
-
You can either * Have two sets of screens, one with the field and another without * Have two field configurations, one that hides it * Adjust the field "context" in the list of custom fields, such that it only appears on Stories
-
Ok, that's a report on failed add-ons, which tells you the basics, but what you really need to read is the actual plugin loading logs, which are above that (By the way, with logs, you'll find it easier to work in plain text - screenshots of plain text are slow to make and painful to read, a copy and paste of the plain text…
-
The file you need is the application log - <JIRA home>/logs/atlassian-jira.log