Nic Brough -Adaptavist- Expert

You need to configure the database to allow the connection. As you've confirmed the parameters for the connection are correct (one thing that used to be a bug was having spurious spaces in the connection string, but I think that was fixed ages ago and a newer Jira won't allow them), then there's nothing wrong in Jira. The…

That's fine, but it probably hasn't got anything to do with your burn-down going missing. Unless * You've mapped the new status into the last column on the board (instead of your done status - like that has become the second-to-last column!) * You've moved issues out of done and into the new status which is mapped to…

You should be able to do it with simply issuetype = Problem as a clause in your search I think there may be more to your question though?

Burn down happens when issues are done according to the board, not the status directly. The board's definition of "done" is simply "the last column on the board". So, indirectly, the status does determine it - the column definitions are "issues in one of these status". My guess is that your "done" status is not in the last…

I don't understand that. If it's not going to be a Jira field, then there's no need to try to enforce uniqueness in Jira Could you explain what this field is actually supposed to be capturing?

Yes you can. Sorry, but I don't think I understand what you're asking now.

Your colleague does not understand the internals of Jira. An issue object is a representation of the current issue, it is not an editable issue object like the mutableissue is. You probably shouldn't be trying to set the description this way either, there's several things your code needs to do to the issue alongside…

Workflows do not exist "in" projects - they are separate items held globally, and referenced by projects when needed. If you change a workflow, it's going to affect all the projects using it because there is only one workflow that you're changing. If you want to change a workflow a project is using, you can, but it will…

Either the parameters you are entering for the connection are wrong, or the database is not configured to allow you to connect from the Jira server or process I note you've used "localhost" in the parameters. Are you really running the database service on the same machine as the Jira server? (There's nothing wrong with…

You will need to talk to the administrators of the Jira system. Either your account no longer has permission to see the projects, or the projects have been deleted. Your admins can tell you which it is.

Your system is configured to use Crowd for its user list, but the connection is misconfigured. You'll need to talk to your administrators about getting that fixed.

You do not download Trello Trello is run as a service, it's not server based software you can run yourself, so there is no download of Trello. People have written clients for it, for various platforms, and you can download and run those on your own servers, but they are not Trello. What are you trying to achieve here, with…

Depends on what type of "child" issue you are thinking of. * A sub-task (child) is part of an issue, the project is pretty much irrelevant for a sub-task, as it gets that from the issue of which it is a part. "Only in same project" does not make sense - to have a sub-task in a different project would be like saying "I'm…

Yes, and you can.

Sorry, I was not as clear as I should have been there. Creating child issues automatically is not "basic functionality".

I suspect you might be asking in the wrong place. This does not look like a question related to Atlassian's Confluence. I suspect you've clicked on "Help with Confluence" (which is what Apache use for documenting some projects), rather than "Help with Tomcat/dspace"

In your first screenshot, you have not put "investigation" into the issue type scheme, so the project does not offer it to you. Sorry, scratch that, it's written completely wrong. You are showing it as in the issue type scheme. But it's not the scheme for the project you are looking at in your last screenshot.

There might be, but it depends on what you think is a duplicate? It can't know that there are duplicates without some rule you define as to what a duplicate is.

No, it can't know what you think might be a duplicate!

Yes, you can, but you will need to install them completely separately - different installation directories, different home directories, different databases, and you'll need to change the ports they are running on.

If you delete an issue, it is gone, dead, there's nothing left of it. If you have duplicates, even if they're linked to the issue you are deleting, it will have no effect (other than removing the link between them)

Story points are a bad measure of performance, especially for individuals.

The issue key (which is what we assume when people say "key" in Jira-speak) will always be unique. If you mean you are talking about another key field of some sort, then no, you can't enforce this without doing a bit of coding that validates people aren't entering more of the same. I'd question the need for this though.…

You can only do part of this. If you go into the Cloud backup manager, you can create a backup of your Cloud system and download that. You can then restore that backup into an empty Server (or DC) install of Jira. However 1. You can't download Team-managed (next-gen) projects. If you want them to come across, you'll need…

I'm afraid that does not tell me anything more about the problem, or further the conversation. What did you see when you checked the searcher?

It could be complaining about any of them, there's no way to know without seeing them! Also, logs usually get rotated or rolled over, you may find the errors have flowed into an archive or been removed, especially if your current log has a lot going into it.

Javascript might be buried in field descriptions or the announcement banner. Apps like Behaviours usually have an admin section where you define what you want them to do - SR injects itself into the Admin menus under the "manage apps" section for example (and explicitly names "Behaviours" as a menu item there)

You need to go to a premium subscription to get Insight enabled (there's nothing to install, just upgrade the subscription and it'll bounce into life)

I'd guess its the Jira Toolkit Participants field, which a lot of people add. It's a derived field, listing the reporter, current assignee and everyone who has commented on an issue, which is quite nice in enabling a search for "stuff I've been active on". But, I cant imagine any use for a report of participants vs status.

Start with a check on the file permissions - are the entire data (home) and installation directories owned by the user that Confluence is running as? (I ask because the errors you are seeing are consistent with Confluence not being able to read its database, but that can be because it can't read/write the config files it…