Nic Brough -Adaptavist- Expert

No, customers don't get to see issues, so there's nothing for them to link to.

Log in as an admin and use the "Backup" function to download a copy of the data.

You'll need to ask the administrators what they have configured for complexity. Yes, it is annoying that this screen doesn't tell us what has been set up, there is an improvement logged to add a display of the current rules to it.

You'll need to take that up with the vendors of the systems you are trying to generate links for.

Start at https://confluence.atlassian.com/doc/writing-user-macros-4485.html

It's not a "problem", it is expected behaviour. The support request may get logged as a suggested change to Jira, but if it is, we'll need Simon to tell us what issue was created - we can't see support requests (JST issues) from other organisations.

What does the log say the reason was for the outage?

You are already doing it. Across the top of the box in your screenshot, you have "my defaults", "filter" and "system". The selection there tells you which one of the three you are changing. In this case, it is the list of fields for the filter. When you save the filter, your selection of fields will be saved with it, so…

The setup in your home directory does not match the data that is in the existing database. Your new Jira is still in a state where it expects to be given an empty database so that it can go through the setup routine. If you are trying to create a new Jira install and connect it to a pre-existing database, what you need to…

Yes, that's the same as the original answer, but you missed off "it is not recommended to do this as it can break some apps" (plus make it harder to migrate to Cloud, as you'll need to re-key the project before exporting it)

This will happen if the files you are attaching are larger than the file upload limit set by your admins. Get them to check Admin -> Attachments (and bear in mind that Cloud has file storage limitations that if you exceed, you will have to pay more for increased resourcing)

Indeed, see the answer above.

Your boards are looking at the same sprint. You'll need to get board 2 to stop including the sprint, and use its own.

No, there's no field like that. But there are issue links, which are more powerful and flexible. I'd use links.

It sounds like you have given your customer a full Jira account instead of just a customer account. Try removing them from the groups that grant access to Jira (you can see these under "manage applications")

What are the symptoms of "can't create"? Are you offered the option when clicking new project? Or is it failing after you start the process?

Your "demand" is not clear. You have found Jira, an issue tracker, but are talking about blockchain, which has no real application in the field of issue tracking. Jira would be a good way to handle your development, testing, tracking and maintenance cycles on anything you are building (which could well be blockchain stuff…

Moving issues is complex because it can change the entire structure of the issue and when that happens, you need to ask the humans what they want to change. I doubt you will ever see a "simple" API for moving issues between projects (or even issue types) The desire to move issues regularly or automatically tells us that…

The heirarchy only exists in Structure technically, but it does a good job of showing you it all, and it looks seamless.

Sub-tasks inherit their version from the parent.

Increase the space available in the repository - you'll need to talk to whomever is hosting it.

Why have you configured your service desk in a way that guides them to do this?

>Each library has its own versioning and release process That pretty much tells me each library should have its own project. I don't think your product teams should struggle with where to place issues - "I need library X to do something" or "I found a bug in library X" - it goes in the project for library X

What is the error response?

If you're using AD to provision users in your Confluence, then all you need to do to add and configure new users is to add them to AD. You'll need to talk to your AD administrators/owners.

Start with a look at what exactly is slow - that will guide you as you where you could enable more logging.

I'm afraid Cloud won't let you inject javascript, and some browser plugin to do it would be a nightmare to write (to cover all the places you can change it in the UI, even before you add apps or use REST) and maintain, let alone demand all your users install it and keep it up to date.

I'm afraid "is not working" gives us nothing. What is not working? What are you doing and what are the responses you are getting?

Let them lapse. 7 days for Cloud, 31 for Server. (For server, you can log in and delete the trial though). Or, click the couple of extra buttons about "you have a trial with us, are you really sure you want to delete"?

Don't bother with SQL, it's the worst possible way to begin reporting on Jira systems. You're going to struggle with this question because: * Boards have nothing to do with projects * So you'll need to look at the queries the boards run * Which are stored in a format you will need to parse for "... and project = x ..." or…