Nic Brough -Adaptavist- Expert

You do not. Jira uses a single database source. You can replicate your database (or database cluster) over to another database if you want, but that will be a backup, you cannot wire a Jira into it until you've made it read-write and stopped replication from the main system. Jira can distinguish between read-only and…

In theory, 7.13 to 8.14 is a single step - run the installer for 8.14 and point it to your 7.13 install. I'd test it first, and if you run into problems, then do 7.13 -> 8.0 -> 8.14 If by "updates", you mean "stuff that includes new features", I would expect to continue seeing them, as they are not stopping adding features…

If you do get an answer from the support call, please share what you can, there are other people finding your question who would appreciate the answer!

So you mean requests (please don't say "ticket", it has no definite meaning and could be referring to several things, including requests and issues) This matters because requests and issues have different ways to interact with emails. As you mean request, what you need to look at are the "channels" for your service desk.…

It will do that if you set up the notifications. You don't need to configure another SMTP server for Cloud to use, it's got one already working.

If you're not using it, then yes, you can uninstall it, but before you do that, blank out the existing key by using the "edit licence" button on the page in your screenshot. Removing the licence should unblock the upgrade itself, but you'll slightly speed up the upgrade if you also remove the application.

What do you get when you visit the issue in a browser? The direct url for an issue is always <your jira base url>/browse/<issue key> so you should find it on https://<your jira base url>/browse/BUGPS_SF-89093 where you'll be able to reassign it or edit it (if you have the right permissions)

You say "ticket" which is totally unclear word. Do you mean your people are replying to emails generated by issue activity (jira users working on Jira issues) or request activitly (customers and agents working on service desk requests)?

Your options are: * Tell the column in the spreadsheet that the content is to be interpreted as plain text (which will be useless to you as it's not human readable) * Do some coding in the spreadsheet so that it understands how to read and display the data * Write an app for Jira that reads the field and shows another…

It will be, when you do the rest of the installation process.

Find and edit the setenv.sh file, it should be in <jira install>/bin You should check that the XXMaxHeapSize you've got in your log above changes to match any new setting

There's no way to do this, the history is a history, not a batch of still-live docs.

GC Allocation failures means there's something wrong with the memory setup. Often, this is "not enough memory to work with". Generally, I'd start by trying to give it more (maximum heap size). Probably increment in 1/4Gb steps

Boards are not containers for issues, they are a view. If you do something to an issue, whatever you do will "affect all boards" because you're changing what the boards are showing you, not the board. If you don't want an issue to appear on a board, you have to change the issue so that the board no longer selects it OR…

No, the unique reference for an issue is pretty much essential for the vast majority of users, so there's no need to remove it, and hence no way to do it either.

This is a good reason to point out that you should not be trying to read the database. It's absolutley not designed for reporting or data extracts, and it's the worst possible way to get information out of an Atlassian system. You have run into one of the reasons I say this - it doesn't have some of the data you are…

Don't confuse "different needs" with "broken working practice".

Atlassian don't do "getting started" type "support" directly. It's probably better described as "training" than "support" as well. Have a look at the training and getting started docs Atlassian provide, and if you still want someone to help you, look to talking to a partner who does training or support at this level.…

The label is irrelevant. What matters is the column they are in (which is determined by their status)

What licence have you installed in your Jira? I ask because we regularly see people who have renewed a licence in their account getting stuck because they have not applied it to their system (many assume their server "phones home" to check the licence, but it does not). Can we rule that out first? Go to Admin -> Manage…

What do you mean "as a link"?

No. If you're thinking of the issue navigator (the grid of issues that shows you what comes back from a search), then you can't do the fields you want - that result view is a list of issues with any issue fields you choose to display. It has no function for displaying non-issue data like project name or start date. JQL…

Linked issues are irrelevant (unless you've set up some form of validation which would prevent the main story moving to "done") For a story to be "done", it, and all of its subtasks must be in the last column on the board when you close the sprint.

I see it fail mostly when * It is used for a project that it does not suit (broadly speaking, this would be stuff that does not readily break down into small individual pieces and cannot benefit from the negative feedback loops that the iterative approach brings to bear) * Management does not buy into it properly - either…

Not on Cloud. On server, there's a trick you can use (create the project, stop Jira, change a counter in the database from 1 to 1200, restart it - I usually tell people never to look at the database, but this is one of the very few things that is safe to do), but you have no way to do it on Cloud. There is a more manual…

Ah, ok, I see. It is the screen size I'm afraid. Yes, your JQL length is causing a problem - the screen layout is built for the majority of cases where the JQL is a lot shorter and doesn't expand the box anywhere like as much, leaving more space on the screen for the results grid. I'm afraid there is not a lot you can do…

You can have many server and cloud accounts at the same time, but the access to each system is independent. You could, given the right setup, have single user accounts in one place (an LDAP or Active Directory type identity provider for example), with each system using that for its user lists. But the access to the systems…

All sorts of things. Without an error message or a description of the "cannot be done", there's not a lot to narrow it down.

Yes.

That's not true, sorry. To mark a sub-task as closed, it should be in the last column on the board (and ideally with a resolution set, so Core Jira sees it as done too)