Comments
-
Indeed it's recursive. Atlassian provide an issue tracker called Jira. They have a public system for logging bugs with it which resides in Jira. If you have issues with that particular installation, then the answer is to log the problems with them, in that same system... If there are problems with client Jira systems (i.e.…
-
Because you don't really need it. Remaining time and logged are far more useful, and in fact, most of the stuff you see in this field is calculated rather than stored.
-
Time tracking is a field that comes out as several fields in the appropriate places. Original estimate is part of it, but in theory, you don't need to see it a lot of the time - you can infer it from the remaining estimate and worklogs.
-
That is often caused by browsers blocking things (pop ups and ad-blockers), but it can also happen if there's something odd with your server setup. First thing, as always, is a look at the Confluence logs, but also the web-server logs, and try a different browser to see if it's that.
-
You'll need to hack the core "view" code in Jira to do it internally. Or use javascript to re-arrange the fields after the screen has been rendered.
-
Yup, if there's nothing in the logs, then it's unlikely to be code. If your indexing is drifting off, then there's going to be a strong suspect in "something else changing the database". I'd be tempted to get your DBA to change the password on the database alongside the same change in JIRA, so that you know there's nothing…
-
There are three ways to approach this * Hack the core user handling code to enable the flag, and then hack the core notification system to be aware of it. I do not recommend that, as you'll be unsupported and need to repeat on every change or upgrade. * Write an add-on that can add the flag for people to set, and write an…
-
Not without some coding. JIRA does not have any flag for "notify me" on your profile. (There is one to say "do not email me about changes I make myself", but that only applies when you are the one triggering the event). So you'd need to code to add that flag, and then amend the notification system so that it destroys…
-
You can't change it without hacking the code behind it. Don't do that, use a filter and a fitler-resutls gadget as Joe says.
-
Standard advice - don't, you're using an unsupported and insecure version of JIRA for which there are no patches and you should upgrade and use the REST interface. However, if you insist, there were some docs for this, but they've been deprecated and I can't find them any more. However,…
-
Again, you need to whitelist the domains, not the ip-addresses, because they may change.
-
We're not Atlassian, we're end users like yourself. Some of us may know some or all of an answer to this, but for a definitive answer, you should ask support directly. However, I don't think you're going to get an answer. The official docs say…
-
No problems here, and if you can't find reports of problems, it's more likely to be something local to your setup rather than Confluence itself. What problems are you seeing?
-
You're going to fail on point 3. A user has to be able to see the issue if they are going to get the email. As your reporter-only users can not log in to see it, they will not get the emails. I've got a feeling they might be blocked from being the reporter in 4 as well.
-
If they're not active, they can't log in to create anything. The best option is to add JIRA Service Desk with a few agents ("customers" are free) This situation is exactly what it is designed for.
-
Taking the database out like that is a good reason for a restart, but yes, it could easily do damage to your system unless you do it correctly.Stop JIRA *properly* (not a "kill")Stop and restart the databaseRestart JIRAThat should prevent problems, as a clean shutdown shouldn't break anything.
-
Sorry, I didn't mean to say "wrong answer" really. It's the "wrong thing to do" - you should not ever automate this. While you're working on the correct thing to do (find and fix the cause), yes, you may need to restart. But if you automate it, you'll be tempted to ignore it because you're seeing less problems on the…
-
No, that is the wrong answer - all the answers you've already had are about finding the *Cause* of the slow down, not patching over a flaw. Don't waste your time filling a crack in a wall with a bit of plaster every time it cracks again, when the crack could be telling you "your house is about to fall down"
-
Just throwing resource at a Java system is often not the answer. It is when you're running out, but doing it without *knowing* that low resources are the problem can make things worse. Restarting the machine is the wrong answer too - you need to monitor and investigate what is really happening before you can fix it…
-
Script-runnner itself is not a culprit, but oh heck yes, the scripts you can run with it are. It's the reason I don't ever recommend the use of script runner unless you have admins who know Jira well enough to be able to avoid writing scripts that can break it.There are plenty of other plugins that can cause problems,…
-
Regular restarts are not the answer! That's just "plastering over the cracks". You need to work out why it's slowing down and deal with the cause of the issue. I've worked with a number of "intensively used" JIRA systems and not needed (or wanted) to restart them for months (and maintenance is for patches, hardware change…
-
I don't think there's actually a question or problem written up here. Could you explain what you are doing, what you see and what you expect/want (i.e. why it's different)
-
That's hideous, you're going to have massive performance problems once it grows beyond a small system, and it will quickly come to corrupt your data. Your index will become damaged very quickly, you're losing session information and, and, and, ... If you persist in running a broken system like this, you are going to need…
-
If you go with a single instance, the best you can do is the DR setup described.If you need more than that, then yes, you need Data Centre
-
Atlassian deprecated some of the useful documentation on doing this when Data Centre was made available. First, JIRA does not cluster. The best you can do for high availability is to have two machines set up with identical versions of JIRA, one being the master which everyone is using. The second one is dormant - JIRA is…
-
Have you tried resetting the password etc?
-
No. Jira sequentially numbers issues. You'd need to rewrite a large chunk of the core code to handle a different scheme.
-
Assuming that is the Jira home directory, then yes - the files in there are created by the regular backups, or by an admin saying "export". If you don't need them because you have more recent copies and/or a database backup, they are safe to remove.
-
What has this got to do with Atlassian products?
-
Yes, a merge is what I'm implying with the "export/import" answer.