Nic Brough -Adaptavist- Expert

I'm afraid that is not an error message itself, it's a marker that goes into logs and monitoring stuff for Atlassian to group together all the different times and places the same problem has happened. All three of you have had the same thing break in the same way on your system. But we don't know what it might be, and…

Welcome to the Atlassian Community! How have you configured the webhook in Slack?

Start with a look at the application log - that will usually tell you what the problem is, usually in a lot more detail than errors.jsp These logs tend to be quite long and have a lot of tracing data for developers in them - you can ignore 95% of the lines in them - essentially, if it's indented a bit, it's part of a code…

Ok, that makes the answer easier! Custom fields for company-managed projects are quite complex under the hood, but the important bit is that they have a "context". The context is where the data is stored and it can be done by project or issue type (or both). The default context for a field though is "global", which means…

Welcome to the Atlassian Community! * See https://trello.com/en/pricing * Not natively, you'll need to do some configuration * Not really, you'll need to do some configuration, although I don't know what you want from an "auto task" system * No, but Trello is not an issue tracker and doesn't really have any hierarchy *…

Sorry, I've been away. You'll need to go administrate the users of your site, adding yourself back in as an admin. Click on the admin cog in your Jira and look for the "user management" option - you'll need to add yourself back in as an administrator for Jira.

Welcome to the Atlassian Community! You can simply add a user picker (multiple) custom field. It won't be the assignee of course, but you'll be able to name as many people as you like in it on each issue. See https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/

Welcome to the Atlassian Community! Generally, the answer is a simple "no" - attachments uploaded to Atlassian software are stored in the location that the Cloud system is running. See https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/ and see how you can "pin" most of your data…

Welcome to the Atlassian Community! There's no way we can tell you whether the backups you have taken and restored are any good. You need to talk to the people who took the backups. The one bit we can tell you though is that if the system is running, the restored data is at least in the right shape, which implies that the…

Are the projects company-managed or team-managed?

Welcome to the Atlassian Community! You'll need your people to use the same account for logging into both systems. How are your systems dong user accounts? Atlassian accounts, google accounts, or with Atlassian Access?

The Jira REST API respects the configuration, so it must be something you have configured. So my question remains - do you see those fields on the issue view when you try the two tests I suggested?

Welcome to the Atlassian Community! Do you mean configuration changes, or issue updates? If it's issue changes, you'll find them all listed in the issue history. If it is changes of configuration, that's less well tracked, but you'll find most of the important changes are tracked in the audit log, as @Mohamed Benziane says.

Why have you created a second resolution field? Why are you not using the standard resolution field that Jira looks at to determine whether issues are resolved or not?

You don't. A backlog is part of a board - it's a list of all the issues that need some attention. The board is the same view, but limited to the items that the team has said that they are going to do, or are working on, or have recently finished. The easy description of the relationship is "a backlog is part of a board (an…

It's a bit deeper than "can't have more than one backlog". The backlog is not something you add to a board, it's a different view of the issues the board includes! You can't have more than one, because the backlog IS the board. The backlog is the list of issues selected for the team's attention. The board is the same…

I'm afraid we're a bit stuck with this one at the moment - yes, we have to fill in a summary and a name. I understand that they're going to be merged (so you just have a summary for an Epic and that becomes its name as well), but I don't know where that is on the roadmap.

Welcome to the Atlassian Community! See (and watch for changes) https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/

No, you should never make it mandatory. If you do, you will have to create resolved issues and you will never be able to make them unresolved. You should however, set a resolution when you close an issue, so that Jira treats the issue as resolved.

Ok, so the fields do not exist on the "issue view" screen. You'll need to add them to it.

True, but be aware that CloudTek are aggressively marketing their tools, and this "report" looks very much like a way to advertise without appearing to be blatantly selling.

Correct, most Jira data is held in fields, properties are quite obscure and little used.

Mmm, that's a good question, when you've got multiple transitions to the same status I am 95% sure that there is a simple answer of "it will use the first one it finds in the workflow definition". So whichever transition was created in the workflow editor first, chronologically.

Yes, you already said that, twice before. Please could you answer my question?

It's always worth following up! :-)

Jira itself does no encryption, it relies on the application server, database, and/or network proxies for it, which sometimes rely on the underlying technology themselves. If, for example, you're doing the encryption in Tomcat, that relies on the Java VM underneath it to do the encryption (and Java supports a lot more bits…

You might want to skim through https://community.atlassian.com/t5/Trust-Security-articles/Atlassian-response-to-claims-regarding-session-tokens-cookies/ba-p/2217925 as well.

See https://community.atlassian.com/t5/Trust-Security-articles/Atlassian-response-to-claims-regarding-session-tokens-cookies/ba-p/2217925

Please see https://community.atlassian.com/t5/Trust-Security-articles/Atlassian-response-to-claims-regarding-session-tokens-cookies/ba-p/2217925

Yes, you already said that. Could you explain where you are stuck? What is going wrong when you follow the steps in the doc you've been pointed to?