Nic Brough -Adaptavist- Expert

I've pointed in the wrong direction as well. The failure is in your admins not meeting the needs of the people using the project. People shouldn't need to be "resourceful" in order to use a tool that can already do what they want. For the pie chart include/exclude - yes, I can see how it lets us down when you have…

Your Atlassian ID is independent of your company, and you own it yourself. You can change its settings by logging in at id.atlassian.com , including the email address. That will not affect your access or history.

What do you mean by "site"? I would guess that a "site" is the url for an Atlassian Cloud stack (xxx.atlassian.net where several applications may be running). Is that right?

It's not a failure of the system to do something with a data type that is not for the type of data you're using it for. It's a failure of your humans, they're bludgeoning a "fix" into something that's the wrong place for it.

No, every entry that goes into a text field has to be treated as different, it doesn't matter if the data in one is the same as another, the system has to assume that they are different items. Your user is botching around a labelling problem here. They should be using labels for this.

There's no way to do that - you've changed the workflow so it no longer has the data that the sprint reports are built from.

Sprints do not belong to projects. They are built from boards which select a range of issues. You need to set up your boards so that they do not select from other projects.

No, it's working fine here. Could you give us more detail about the problem you're seeing? What does "not connecting" look like?

I'd ask the people who are asking you to use the board.

Absolutely not - each node would have corrupt data the instant the other one wrote anything to the database.

You'll need to look to the mail server to see why it is not authenticating.

You'll need to ask the owners/administrators of the board.

No, you've missed the point again. Multiple assignees is not the way to address what you're talking about here. I have yet to encounter any place where multiple assignees does not cause problems. I've had this discussion many times here on the community, and on one of the longest discussions from years back, I've had three…

Change the project permission scheme such that no-one has "edit all comment" permission (maybe leave them with "edit own comments" permission) Note - I do not know if permission schemes function on the free cloud version of Jira. If they do not, then you can't do this.

Put conditions on the workflow that say "assignee only"

Sorry, what issue? The system is offering you what you have asked it to - the ability to secure an issue based on group membership. I'd say if you think you want more than a handful of security levels, you're doing something wrong and should re-think what you're using it for. Why would you have thousands of levels?

Are there really no errors in the application or server logs? When it dies, what are the last few records in <confluence home>/log/atlassian-confluence.log and <confluence install>/logs/catalina.out ?

I do not know the roadmap for this, sorry. I think it's safe to say it's "not soon" though (as in probably not this year)

No, there's no way to do this directly. A user has to be able to see the issues in order to report on them.

I think you have not read any of the explanations of why this is not in Jira and why it never will be.

No, the issue create process can only start after you've given it a project and issue type. You can't create an issue from the data in a custom field natively. You can do it with code, but that code will need to work out what project and issue type to create from the custom field data.

There has never been an option for copying child pages. You may be thinking of delete, move, or functions provided by an app. If you want to copy a page and its children, you'll need an app to do it.

I think by "initialise", you mean "pre-fill content". Two points on that * Do not do it. Far too many people will just click through it and leave you with a useless set of data. I am utterly utterly sick of people who default text into fields and then come to me two years later complaining that 80% of their issues are…

Because "copy page" does what it says - it copies the current page. Child pages are not part of the current page.

You'll need to look at why your email account is refusing authentication.

What does the log on that node say the problem is?

What code have you written, or what app are you configuring, to do this creation?

This does not tell us anything about what you want to see. If you need an "audit" on an issue, look at the issue you want to audit, it has an issue history.

Again, clone simply creates a copy. There are no functions for choosing arbitrary data to change on the copy

No. Sub-tasks are not limited by the parent issue type. グーグル翻訳から： いいえ。サブタスクは、親の問題の種類によって制限されません。