Nic Brough -Adaptavist- Expert

This can happen on server when something gets corrupted in one of the two places workflow is held on an issue. You can fix this by running the integrity checker - it can find and be told to fix these.

This does not tell you that the "wrong code gets executed", it tells you that you are making the wrong call with your other application - it's hitting the wrong place and calling the other endpoint.

Welcome to the Atlassian Community! The code you have been given there is not directly an error message; it is a marker for Atlassian to gather together more information about the underlying error (it may have happened to other people's systems, and they'll have been given the same code). They'll use it for scanning logs,…

Welcome to the Atlassian Community! You do this with the page hierarchy, space permissions, and restrictions. In the most simple case, look at the space permissions. These apply across the whole space, so you don't need to think about sharing or copying permissions down. Add a new group to "can use space" and everyone in…

There is not really any "server" or "data center" version - they're running the same code. A data center install should be done a little differently to a server install, but you can actually stick a DC licence on a server and you'll get everything DC does (except the cluster, you'll need to do quite a lot of messing with…

It's not possible, each Cloud site is made up of a single Jira and/or Confluence. Also, a Jira can only exist in one place at a time.- you can't put project A on one domain and project B in another on the same Jira. Best you can do here is use project categories to tell people where each project lands, but that doesn't…

An issue will move to the next sprint when it is not done when the sprint is finished. To be done, it must be in the last column of the board (and, also, all its subtasks must be too) I note J Hammond moved the status from "Done" to "released". My guess is therefore, that released is not mapped in your board (because it's…

This is not a global setting, it's done on a request by request basis. You say it started happening when some people were removed. That leads me to think that your mandatory fields were user fields and set to default to one of the people who has left. Now they've left, Jira can't set the value, and hence they fail the…

Welcome to the Atlassian Community! Not quite, but you can get a partial impartial implementation of it. Sprints do not belong to projects, they are artefacts of a Scrum board. Process Management projects don't have Scrum boards, so you can't do it that way. But you can create a Scrum board in a Software project (or a…

This is not quite what issue security schemes are for, and they can't stop people creating issues. There's an error somewhere in what you say here, so I'm not sure what you have actually tried to do. You say "I created an Issue Security Scheme and then an Issue Security Level that states only project users cannot create…

If the "activate" is not appearing before the error, then the error is not coming from your script, it's something else doing it!

Welcome to the Atlassian Community! Your confluence.cfg.xml is broken, you'll need to correct it. Make sure you edit it with a plain text editor and that the XML is in the right format.

Ok, you will have to reconfigure all the projects currently using it, make your edits and then re-associate it. That's not the best way to do this though, because it's two migrations and needs another workflow to temporarily associate. A better option would be to make a copy of the workflow you want to edit. A copy will…

I'm afraid all you can do is talk to the current admins of the place where you have lost rights. I would want to check if you still have site admin first - go to my.atlassian.com and log in with the account that used to have admin. Is the second site listed under your products?

See Dirk's JQL he simplified for you.

Sub-tasks have no use in a Scrum backlog (they appear in Kanban because Kanban sees a sub-task as being something that needs doing, just like a standard-level issue. It does not really do anything with sub-tasks). * You don't rank sub-tasks outside their parent issue, because they are a part of the issue, not sprint items.…

It's for Agents to tell us whom they are raising the request for (imagine an Agent is on the end of a telephone and the customer is explaining the problem, rather than going to the portal or email - the Agent will want to record who the customer is)

Welcome to the Atlassian Community! You simply can't do this. Every app injects different things in to Jira, and hence could be used in all sorts of different ways. Which means each app would have to include something that reports on how it is used itself. Some, of course, do do some tracking, some have some functions that…

@Jack Brickey already said most of what I wanted to say, but I do want to add that I think through how I want to be using the data, through two simple guidelines. * A board is a team's work * A project is a way to group together a load of issues that have common processes and data (fields and workflows) As a board can…

"timeout" here means that the plugin is trying to initialise, but taking far too long to do it, so the JVM is giving up on it. You will need to put logging into the plugin to enable it to tell you what it is doing for the 3 minutes Jira gives it to load.

Welcome to the Atlassian Community! This sounds like one of the admins of the second organisation has removed your permission to be an admin for the site. This might have been done if they've claimed the domain for their organisation and the email address on your Atlassian account does not belong to their organisation or…

This applies to company-managed projects and boards too. An issue is only "done" if it is in the last column of a board. The non-board parts of Jira look at the resolution - empty = unresolved, any value filled in = resolved. Most of us try to keep the resolution in line with the status - if the status puts it in the last…

Yes, but no. All you need to do is not give the admin "use space" permission in the space settings. But as an admin, they will always be able to admin a space and add themselves back in.

Welcome to the Atlassian Community! No, there's no way to do this, the publish function publishes what you've all been working on together as it is now.

FWIW, the usual culprit of chewing up disk space is attachments. As @Thiago Masutti says, you need to look at what disk space is being consumed - are you sure it's the databases?

Ok, so go into the space permissions and look to see who has access with a licenced account. The space permissions will not list customers as an option. But the box you have ticked there also is quite clear - "active users" means "people who can use Confluence". It does only give them "read the KB" though, nothing more.…

It gives you control over all the additional features Premium gives you.

A couple of people commented when I used the bookshelf background. One asked me if I had moved house, another asked me if my kids had enjoyed building the Lego models (no, but I did), and the third asked how I had got so much Atlassian swag!

> I understand that if there is "or", then condition 1 is checked, if one of its clauses is not fulfilled, then condition 2 is checked. Is this true? No. Both clauses are evaluated at the same time. There's no stepped procedure here, both clauses are checked. An OR join does not do "If A = false, then evaluate B", it does…

Welcome to the Atlassian Community! Jira's standard hierarchy is just "issue" -> "sub-task". Issue is the general term for all the types of items that might be used (Jira lets you create many issue types and call them what you want. If you're trying to be agile, I strongly recommend going with Jira's default issuet type of…