Nic Brough -Adaptavist- Expert

I'm afraid this is not a standard function, and your screenshot that could help us identify it does not work. Could you give us a working screenshot?

I can see that your needs are a bit more complex. * You are absolutely right about one excerpt per page. It's because of that I have developed a habit of writing quite short pages and then pulling long pages from many short ones, rather than few, longer pages. The "multiple excerpt" macro in the marketplace is well worth a…

You will need to explain what you mean by "CSP" and what it has to do with Atlassian software.

Some fields have a "default" you can set. Description is not a field that does. Generally, it is a bad idea to pre-populate text fields - you end up with huge swathes of totally pointless copies of the pre-populated text (I once found 40,000 issues with identical descriptions - utterly useless)

What "type" of custom field are you adding?

Wikipedia's redirect system is quite weak, compared with Confluence's "include" and "excerpt" functions. Have a look at the include and include-excerpt macros - they allow "edit once, show *everywhere*" functions that most wikis do not.

<sigh> Many times, because you have no idea. Ask your admins to do their job, as we've said many, many, many times before.

>"why don't we just have folders?" issue. Because you already do, they're just called "pages" instead. Unlike most of the other people in this conversation, who really have no idea how information really works and becomes useful, you have said some things that do make sense. Just to kill off the main thing - "folders" are…

I am sorry, but it does not help. Could you try to answer the clarification questions? We don't expect to get it right next time if you do try to explain, but please do try - any explanation is likely to get us closer

Wikipedia's redirect system is quite weak, compared with Confluence's "include" and "excerpt" functions. Have a look at the include and include-excerpt macros - they allow "edit once, show *everywhere*" functions that most wikis do not.

Confluence does not care about file types (unless you have added and configured something that does). The error message you are getting is saying that you're trying to attach empty files. My best guess is that your OS sees them as bad files and is not sending them up to Confluence, or seeing them as something it should not…

It's not a "klduge", it's "using software properly". If you need to assign issues to people and track those issues, then that person should be represented in the tracking system. So use it properly, give them an account and assign the issues to them. Don't "kludge", just use it properly.

There are no functions for this in the main software. There are some apps that can provide it though, have a look in the marketplace. There are also some that can help you with integration with software like Teams.

All of the speed problems I've seen with Cloud have been down to: * Temporary problems with Cloud servers (rare, and don't last long) * Really bad configuration ("Fielditis", pointlessly long workflows, bloated lists of dropdowns that people just stick random data in because they've got no way to work out which option is…

It depends on what you mean by "integrate". If you have a Jira system already, by far your best option is going to be to add Jira Service Desk to it. But that is a single system, which will be either Server, Cloud or Data Centre. There is no way to add a Cloud application to a Server install (or vice versa). If you could…

Yes. Jira doesn't care whether a human types things in, it gets poked in over REST, or you import the data. Reports are available, no matter how the data got into Jira.

Don't put estimates on sub-tasks, it does not make sense and Jira ignores them.

The files in "export" are exports of data, for backup or migration, you do not need them to run Jira (I usually set up a "log rotate" to clear out older files in there, if the admins have not turned off the regular xml backups)

Sorry for the delay, I've been swamped. If the html file does not work, then Apache is not configured to serve it up correctly. I'm afraid I can't tell you how to fix that, I don't know what your config is.

Sadly, no, the Clouod audit log has dropped "issue delete".

If you were on server, you would have the option to edit a properties file to disable "relative dates". This is not available on Cloud.

If you have enabled the admin audit logging (use the function search in the admin section to find it, look for "audit"), then it records "issue delete" with the key, person and date/time. But not the content.

The story was not "done" when you closed the sprint. To be "done", a story must be in the last column on the board, along with all of its subtasks if it has any.

No, I do not. What are these "crashes" you are seeing? What are the error messages and symptoms?

Nothing was done, as there is nothing that can be done.

Could you tell us what app you are using to provide this function?

Make your "master" page a series of "include: child page X" macros instead of a block of copied text.

You do not. If you remove a story (from a sprint), the reporting is going to show that, because reports are there to show you what happened. So * Yes, because you have effectively said "it's done" * No, because it does affect burn

It can "accept" all file types as attachments, and will do so by default. If you've lost an attachment, it's going to be because something on the server not liking it, not JSD

What do you mean by "export"? Export usually means "give us data", not "give us formatted data". In most cases, it's up to the receiving program to do formatting, not Confluence.