Nic Brough -Adaptavist- Expert

Right. So have you reported this? Is it possibly fixed in a later version?

You cannot report on something that is not there. Deleted issues are, well, deleted. The only way you can know that an issue was deleted is to look at the numbering. If you have ABC-123, ABC-124, ABC-126, ABC-127, you can infer that ABC-125 has been deleted (but you should check if it has not been locked away from you by…

Again, if you did not take a backup, there is nothing you can do. Your changes have destroyed what was there before. To "revert", you will need to edit the workflow again and, from memory, put it back the way it was.

Cloud does not handle licences this way. Are sure you are on Cloud?

I don't know what your original workflow looked like because you have not given me a copy, so I cannot offer you any help going back to it.

So there is a networking issue. Check that you're not firewalling it off, and that the server is configured to allow connections from the remote machine.

The scripts were probably there before the upgrade, but most of the older versions of Jira would not display them when you look at the field configurations, so it's understandable why you thought they were not there.

Your query, in plain English, is not quite what I think you mean it to be. You are asking for "all CS Incidents that have been in a status of Open in the last 7 days" I think what you want to ask for is "all CS Incidents that were created in the last 7 days" The difference between those two is quite significant - the first…

Without a backup, I'm afraid there is nothing to revert to. You'll have to manually undo the changes you made by putting them back the way they were from memory.

Absolutely, there's quite a few places using Confluence for user manuals, and not just for software manuals either. If you want to use the $10 per month Atlassian Cloud offering, that is all hosted for you, immediately available to the world, and is quite customisable - company and product logos are no problem and you can…

Hmm. Are you using issue name translations at all?

Did you take a backup of it? 

Your database is not running on the server you are trying to connect to, or there is a network problem between your Jira server and the database server.

Re-read the query. In plain English (and remember that punctuation matters), you are asking for All bugs with a fix version of release 1 in project eagle, or anything with release 2 or release 3 on it. I think what you actually wanted to say was All bugs in project eagle with a fixversion of release 1, release 2 or release…

Those scripts were placed there by your admins (presumably inexperienced ones who didn't know they should not be botching things with javascript like this) You are already doing the right thing by removing the scripts from the descriptions.

Ok, now could you tell us what you did as a workaround and hence why it has stopped working?

Could you show us the list of issue types in the issue type scheme for the project and what you get in the selection list on create?

This suggests that you are trying to run it on a port that is either privileged (and the user running it does not have the right to run on that port) or something else is already running on that port. What port is it, and what does netstat or ss tell you is already running there?

What issue with resolution date?

Where does it say you do not need to edit the server.xml? Could you please follow the documentation and not diverge from it. Then retest? If you do what the doc says, it will work.

The only thing the burndown looks at is "is the issue done?". That means the "done" column on the board - the last one, whatever you choose to call it.

Your question is unclear. Are you trying to upgrade Confluence, or the database it keeps its data in, or both? Why are you reading docs about migration, instead of upgrade?

The error message here is clear - you have not made the changes required in server.xml. Take another look at that file. For what it's worth, most people who ignore that part of the doc either don't read the bit about commenting and un-commenting the right section, or they don't read the bit about the port number and pick a…

* None. It's not limited by user or company * Yes, you can always ask your server admins to add disks to your servers * Not applicable, see above * All data takes up space. Attachments take up simple disk space, pages (and blogs and config etc) go into the database, which also consumes disk space.

You would be in breach of your licence agreement and may see your system fail.

You will need to find or write an app to provide a field that does this. I am not aware of any app in the marketplace for this though.

No. You will need to log into your my.atlassian.com account to get the key to copy and paste into your server's licence box. I do not know if Clearvision might get the key for you and send it on via email or something, but they won't have access to your Jira to do anything automatically, unless they're running your system…

A board is a view of a set of issues. If you change an issue, then any board showing that issue is going to show that the issue has changed.

Correct, 10 user licences are not entitled to developer licences

Other usage of a status is irrelevant to the current team (board). You don't care how other people might be using it. The status category is shared, but but does not affect what column your team puts the status in.