Nic Brough -Adaptavist- Expert

I am sorry that this is going to look really bad, condescending and patronising, but the answer is "click site admin" If you do not have that option, then you will need to talk to your site admins.

I'm sorry, but that is totally self-contradictory. You can't see a numbered list button but you see it in the formats bar? Which is it? Is it there or not?

Welcome to the Atlassian Community! That error code is not really an error code, it's a marker that's being written into logs and databases when the same thing happens in many different Cloud systems - Atlassian are gathering the errors together so that they can fix it for everyone and report back to anyone who has run…

Welcome to the Atlassian Community! This is not an Atlassian supported system, you will need to talk to the owners/administrators of it (whatever the problem is, they would be the ones who would raise a support request with Atlassian if they can't fix the problem) The URL you have for this system is for a server…

Welcome to the Atlassian Community! Short answer is that you don't. There is no "export config settings" other than taking a complete backup, which is only then useful for creating a copy of the system. What are you trying to achieve with your "export"? We can probably talk through options and tools to help you do it, but…

Edit the field in the issue, highlight the lines with numbers and then de-click them with the "numbered list" button in the editor's functions bar

Not a simple one. The workflows are not stored in a database format, you'd have to read the workflow table, get the XML from each one, and then parse the XML to find the IDs of each status in use, then join the ID list with the status table to see their names and categories etc. A flat list like that is not really going to…

Welcome to the Atlassian Community! What do you mean by "scribe"?

Solution to what?

Mmm, if you're going to log time automatically like this, then why are you bothering to log time?

If you think this is a malicious email, forward it to https://www.atlassian.com/trust/report-abuse and ignore it.

No, you have explicitly stated that you want to lie about whether an issue was in a sprint or not. Could you explain what report you actually want to get here? If it's a useful one, it won't need to lie about the issue and sprint data.

You need to look again at your database config. The collation is still wrong (but that will only break some searches, it is not a huge whoopsie for Jira now

Yep, you can prevent people from doing that by setting up the workflow so that it does not have the transitions that would let them move issues to from the unmapped status to a mapped on.

The answer has not changed - you need to set up your database correctly. Fix the collation settings, and you'll be fine.

There's no warning pop-up because working this way is not a good practice and you are not expected to work in this poor manner. The right way to work is to either have all the status mapped, or to not have a process that allows users to move an issue from an unmapped status to a mapped one.

Mmm, so you want your reports to lie to your users? Is that really a good report?

I'm going to be lazy - https://community.atlassian.com/t5/Jira-Software-questions/Changing-an-account-from-managed-to-unmanaged/qaq-p/1352355 covers 90% of the conversation! TLDR: start by asking your admins to change the email address on your account!

I'm sorry, I need more explanation. A listener will pick up an event and (maybe) make a change to an issue. A REST API call will ask a system to do something. Even if someone clicks edit at the same time that one or both of those are running, they'd need to be doing it within microseconds of the other actions for a…

Well, that's not how DKIM works, but Atlassian won't send emails to people who don't sign up for them, and their systems will only email your users when you configure them to do so.

Welcome to the Atlassian Community! Could you explain what you are trying to achieve here? Of what use would this field be to your users and reports? Why is the issue key, or even issue id, not the right thing to use for a unique and sequential identifier?

Welcome to the Atlassian Community! Go to id.atlassian.com and into the "profile" settings (top right, your user icon), you can change your display-name there. I'd strongly recommend using a more human name when you do this. Using an organisation name (like Roblox) exposes you to accusations of misrepresentation, and…

>can I proceed with my JIRA upgradation by ignoring these erros NO. With older versions of Jira you could get away with it, but from the mid-7's onwards, it became less tolerant because dealing with mis-configuration just became a massive coding time-waster. You need to set up the target database in a supportable…

That issue is one that Atlassian should have closed as "working as intended" when it was first created. If a status is unmapped, it can't be in the sprint. It's nonsense to do it any other way. I suspect the issue is left open just as a reminder for Atlassian to make it more obvious what is happening - either by…

You are changing the scope of the sprint when you move an issue into or out of it. That's half of the definition of scope change (the other is changing the estimate on an issue in the active sprint) By definition, an unmapped status is not in a sprint. The mapped status are. So when you move an issue from an unmapped…

Welcome to the Atlassian Community! I don't really understand the question. One of the great things about Jira is that it does not allow you to use the terrible anti-pattern of assigning an issue to a group (because it's always a disaster in real life) So, the question is, how have you botched an "assign to group"…

Welcome to the Community! I'm afraid that none of that makes a lot of sense. >I cannot see the "Tools" option. Unless you have a read-only account, there is a tools option menu towards the top-right of the page. In the last four years, it might have changed its name and icon, depending on what you've upgraded or migrated…

Sorry, how do you find what?

That's not an issue, it is just warning you that you are trying to bring an un-estimated issue into the sprint, and that if you then fill in an estimate later, it will look like scope change.

Yes, you already said that. Could you explain what it has to do with Confluence?