Nic Brough -Adaptavist- Expert

It's not "not ideal scrum", it's not doing scrum at all - sub-tasks are irrelevant when it comes to doing scrum estimates. If you're going to do that, then you need to think through a scheme for accumulating estimates on sub-tasks up to the parent and matching them to the story estimates. Jira has no support for such…

There's no point, you can't just jam the developer or newly generated licence into the database and config, you need to trigger the code that evaluates it too. Use the REST API licence validator to check the licence first, then you'll be able to add it.

You can use "text ~ xyz" to search all the text based fields, but select list fields are different and can't be searched like that, you'll need to name them separately.

The licence goes into the property table and also a file on the file system. You should not be looking at the database though, to work on anything - if you're thinking of moving things around, your licence will need to change anyway. Yes, the xml backup is defaulted to twice a day. If you've got a production system or just…

Have you started the service locally? If you tried to start it and it is not serving pages, then what does the log file say the problem is?

It tells you about the security level set on the issue (security levels restrict visibility of an issue to sets of people)

Your systems are no "configured the same". Either the proxy or the service behind it are configured to use the outdated protocols. Check the system settings and the proxy settings.

This means you have signed up for a Trello account and used it at a level that you need to pay for (i.e. not free). The payment you've made here is the bill for your usage. Go to trello admin to see what your account says and how you've used it 

You should be able to get whatever is monitoring the cron failures to poke issues into Jira over the REST API. (I don't tend to write complex cron scripts, and just use more scripts to check logs, or build the error trapping into them)

Create a permission scheme that doesn't allow for anything other than "users can browse project". Then swap the target project to it when you are about to migrate. People will be able to see the project, but not alter the data. You probably want to leave it that way as well, if the users are moving to Cloud.

Only the error messages for validators are configurable by admins in the workflow.

Your offline DC Jira will not be able to talk to Opsgenie, as there will be no route between them. So, no, this won't work.

No. Teams is a way to talk (chat) with poeple. Jira is an issue tracker.

Jira has a direct export to CSV which generates files Excel can read, but if you want to do the work in excel rather than use those, your macros should call the REST API in Jira to pull the data out of it.

Burndown shows you the velocity of the sprint, team velocity is the overall velocity of the team.

Ah, yes, ok. Team-managed projects don't have the convert option for their issues.

Not sure why you would clean out this directory completely (Jira will just fill it with copies on restarting, slowing the restart and chewing the disk space back up), generally, you would only really want to kill off files in there that have been left behind for no particularly good reason, having a rule like "remove files…

Changing an issue's type is a structural thing, and you can only edit or move an issue to another type at the same level. Changing an issue to a sub-task type (or from a sub-task to an issue) is even more structural, as you need to create a relationship with a parent issue, or destroy that relationship. You don't do it…

Please STOP SHOUTING - it is hard to read, and a lot of people find it very rude. Jira can be used to run a project that is about a garden, like any other project. But you will need to explain what ABP is and what it has to do with Jira if you want any help with that. ( I do not see what Associated British Ports have to do…

Managed accounts are owned by an admin (or set of admins). You can't delete the accounts, you need to ask the domain admins to do it.

JQL is for finding issues, not looking at their data or reporting on them. All we can tell you to do with JQL is "use it to search for the issues you want to report on". Then you can push the results through some reporting.

So your problem now is that you aren't being shown something you can easily infer from the fact that an issue is in front of you? You know you can put that status on the cards in the backlog too?

Um, no, it was actually one of your comments earlier that "strawmanned" it. And a strwman is not a bad thing - it is there to frame attacks upon it with clarity. But let's move on from that logical failure and look at your points: >We do not want "backlog with seventy eleven states", or "a hundred and eleventy twelve…

Look to your browser settings. Jira can only go on what your browser asks it to do.

One of my friends has a cover band, most of whom are geeks. One of their covers is broadly: Millions of kitties, kitties with me...

I disagree - the law should say "you can put anything you want on pizza, as long as all the consumers of the pizza are fully aware of what (might) be on it and hence able to make informed choices as to whether it is safe, edible and nice for them". Of course, if it has pineapple on it, it's not safe, edible or nice. To me.…

I do understand that some of the stuff said here comes across as condescending. I do know my some of my writing looks that way. I can't defend my style, it's just the way I write, but I would like to say that I do not want to be condescending and I am sorry that it has turned out that way. I am trying to explain and help,…

My instinct is to dig a bit deeper - why would you want to automate a structural change like this? Categorisation of projects is something that always requires a human to think about it, and it something that is so infrequent, even typing your question has taken more time and thought than you'd get back from building an…

It also depends a bit on your intended usage. Imagine you've got three teams, A, B and C. You're migrating team B to Cloud only. You don't want down-time for A or C, so you leave it running, but from the point at which you copy the data out of the Server, until it is fully loaded and ready to use in Cloud, then team B will…

That error code is not really about an error, it tells us, the end-user, nothing. It's actually just a marker in the logs and data for Atlassian to look for when you report this error to them. It's likely more than one Cloud system is seeing it, as it's referring to an error that's common to many systems. All we can do is…