Nic Brough -Adaptavist- Expert

It is "strictly evaluating" the JQL. You are looking in the wrong place for a "fix" to this. JQL is not SQL, which is something people misunderstand a lot. A JQL query gives you nothing more than a list of matching issues. It really is just the search part of what you're doing. The JQL has nothing to say about the data it…

It is not quite possible to tell what you need to back up from the file system alone. A minimal backup of Jira or Confluence contains * The attachments * The database That would allow you to recreate your Jira or Confluence into a new empty system that you'd install from scratch. It would need some work to configure, but…

Which gadget are you using for this?

Do you mean * the name of your site (yourcompany.atlassian.net needs changing to newcompany.atlassian.net) ? * Jira issue content in fields ? * Jira project settings ? * Confluence Knowledge base articles ?

The reason your backlog does not contain sub-tasks is because they are simply clutter. The backlog is for ranking and sprint planning, which subtasks have nothing to do with. In fact, you can see them in backlogs - add the "sub-task" field to the backlog card display. Of course, you can't actually do anything with them…

"Additional task provided" is not a reason why. Why do the people asking you to do this think there is a reason to do this? What purpose is there behind it? Why do they think this is worth doing? What is the benefit? What benefit would a popup be to the end user?

No, that's wrong. Please stop looking at the database, the data in there is not helpful for sizing (or much else) You need to look at the active user accounts. Add up the number of Agents, Developers and Core users.

But why do you want to automate it? What is the reason?

The version of your Cloud system is not too easy to find, the best way to do it is a "system information" call made over REST. But, it changes frequently, and it doesn't really have any use to anyone apart from some awareness of REST API changes and very specific bugs which are not your problem, but Atlassians! It's pretty…

I've asked Atlassian to look at it in Slack, they should know it's the same error for more than one site!

You've chosen a full import of everything from a (Server?) xml export file. This will overwrite everything in your Cloud system, as that is what it is for - restoring a backup or cloning another system (for test or migration) You should instead be importing just projects, which is not part of the "restore from backup"…

There's no way to do this, Behaviours can't get to that drop-down. It's also hard-coded, you would need to amend the core code inside Jira to amend the lists on offer at that point.

Nothing to do with this error then.

No, that's unrelated. What error are you actually getting?

No, that's a totally different error.

Ah, sorry, we're a bit stuck then. The problem is something that has happened on the back-end, inside the Jira system you are using, and the code given to you is generated by it, just to enable Atlassian to find it quickly in the logs and data. But if you're on the free plan, there's not a lot we can do - we'd need…

Yep, if you're not an admin, there's not much you can do here. It's your admins job to get your Jira set up in a way that works for you, so if you need to get its behaviour changed, you'll need to to talk to them more.

It's an error reference to give to Atlassian support when you raise a support request with them.

It depends on how your Jira is set up - if your workflow has a transition that clears it, then you could push the issue through the workflow until it goes through that transition. There may be a flag set on a board for a column to set or clear it, in which case you can drag it across the board there. But really, you need…

You would need to write an app to do that, I don't think you could write a parser in velocity

I have tested, which lead me to the answer given above.

Do not use SQL to do this, it's the worst possible thing you can do, as you can tell, as it's not worked for you.

Correct

For someone to be a reporter of an issue, they must be a Jira user. There are a number of ways to take a list of people and add Jira accounts for them, but it does depend on how you can get an export from whereever and what provider you are using for Cloud (are you on Atlassian Accounts, Google Accounts or Atlassian…

How are you defining "products" in Jira?

Ok, which filter causes it?

Note the box at the top of the doc - this kludge only works on Server and DC. Cloud does not allow for it.

To drag and drop, (including into a sprint), you need to have the filter sort order to be set to "rank". The issues that don't have "sprint" - could they be sub-task types?

Yes, those flags are to tell you that you are looking at the one the system has built in. The others are ones added by your people.

When exactly do you get this? Is it when you first navigate to the board, or when you try to do something on the board (move a card, click on one to view it, hit one of the view options, etc)?