Nic Brough -Adaptavist- Expert

Ok, that is almost certainly a damaged H2 database. You'll need to install a clean Jira and restore from a backup.

A quick look at the logs would be needed to establish exactly why the database is not reachable. Start with <Jira home>/logs/atlassian-Jira.log - that should give us a pile of text that contains a detailed reason for the disconnect. However, this is likely to tell us that your database is broken. H2 is not reliable,…

The docs probably aren't inaccurate - could you tell us which one you think is not accurate and where you are stuck?

Absolutely the right place to start asking (it might end up as a support call with Adaptavist, but let's start here with the wider audience!) At what point do you want to enforce this rule? 

Thanks for the detail, the main thing I wanted to check there was that it was the built-in export that I also use sometimes, so we're looking at the same thing. There could be other ways to do it, but we shouldn't need to worry about them, let's stick to the off-the-shelf one. The standard export drops out a compressed…

Yes, but it's a browser function, nothing to do with Confluence, and if you have an object that needs editing in a certain program, you're going to have to download it for that program to be able to open and edit it (even if it doesn't look like a download, you still have) But no, the doc does not have to be attached, you…

Yes, but it is a bit convoluted and needs some design and planning. Also, it's not done with the board. A board is a view of a selection of issues. Each column in the board is a collection of status (often a single status), so you need to start by looking at the board config to establish which status makes an issue be in a…

Ok, so what do you mean by "no aws service management connector in jira managed apps"? If it's not in the list of apps, then you have not installed it.

How are you doing the export to html? Have you tried opening the downloaded html in a text editor instead of a browser? Also, could something have been compressing the download?

Yes, that's how I would do it. I'm not 100% sure of your code, I don't do a lot of coding and have to look stuff up all the time when I do, so I can't validate it. But you've definitely got the structure right, and it does look like it should work. (I would change one little thing - I'd move the "if project" check way up…

No, there's no way to do this, Jira always uses the email addresses it has been told to contact people on. However, if you have disabled the email in the recommended way (step 8 in https://confluence.atlassian.com/adminjiraserver/creating-a-test-environment-for-jira-966063324.html is a load of environment variables that…

Hmm. You know, I'm not sure. I thought Due Date was a date-only field (but, be warned, I do not have a fantastic memory, it's more like one of those thingies with lots of holds in it Technically, it's still a date/time field really, but date-only fields always store date+midnight, so your batch of issues due on the 2nd…

Welcome to the Community! In almost all cases, Confluence crashing will be writing the reason into the logs. Also, if you can't restart it without rebooting the machine, it will be telling you why it is not restarting, again, in the log files. Start with a read of <confluence home>/logs/atlassian-confluence.log - that is…

A sprint will appear in a board if there is an issue in the sprint that is selected by the board. Your two boards both select for your unassigned issue, so when it goes into the sprint created in board 1, it causes the sprint to be shown in board 2. >I am wondering if there is a way with JQL to have all tickets in future…

It is not clear what you are now asking about, sorry. Could you explain where you are stuck, and exactly what you are doing?

No, I get the problem, you are unable to link an issue to another. Everything you describe is consistent with you not having permission to link and edit the target issue. Or, possibly, you have an app stopping it.

This is a question you'll need to ask of the project owners or system admins. Someone has added this "Name" field to your Jira, and we can't tell you what it is for, we don't know your system!

The same answer applies - you'll need to add the fields to the request if you want the customers to see them.

Neither of those can happen. When you delete an issue it is gone, you have destroyed it entirely and there is nothing left to work with. Your "restore" is not restoring the deleted issues, it is creating new issues - that's why the counter carries on going up, Jira increases the project's issue counter for each new issue.…

The APIs don't either, but you can easily script to call the delete project function repeatedly over the APIs

You haven't got jq installed and in the path in that set of commands, and it has nothing to do with the error you've asked about either. Could you stick with one thing please? Do you want to fix the problem you originally asked about, or debug the new thing with the jq error?

There isn't a way to do that other than getting the browser to support it - a server should never be able to run something on a client machine unless the client machine has been deliberately configured to support it.

You do not. Or rather, you can, but it's not a fall-back, it's "start up the other system and use that instead of the original one" This is unless you are actually talking about Jira Data Center, not Server?

What is the problem you are having here?

Possibly, it depends on what you're migrating, how much and if you're willing to accept the way JCMA will migrate config.

I can't tell you much more than "use a transition to change the status" - you've not explained what a PD Jira is, or described your workflow, so we're having to make generalised assumptions and suggestions.

If you delete an issue type from the projects issue type scheme, Jira will walk you through migrating the existing issues of that type to another type.

You can't do this - as you've discovered, components are project items, and your metadata issues are in a different project to the ones you're trying to document. There are a few options: Drop components from the metadata project and use a custom field for them Add all the components from the other projects as components…

You are creating new variables in the parameters when you are saying "type name" (object value and customfield customfield) You should be just passing the variables that you've already created into the call, not creating new objects. Remove the type definition bits in the call.

To change the status of an issue, you use the transition that takes it to the new desired status.