Nic Brough -Adaptavist- Expert

No, there's no function for it because it's a bad thing to do in a sprint - issues should be created in the backlog. Changing the sprint commitment during the sprint should be a rare exception, not a routine thing.

How are you trying to do the migration? Does your account have the permission to read the project (browse project permission)?

Neither of those things can be done on Cloud - Atlassian have no plans to implement anything like this in Cloud, and Cloud doesn't yet support the stuff that apps would need to be able to do it.

Confluence can be used for this, but I would strongly recommend looking for a diagramming app to add to Confluence to make it a lot easier.

I'm afraid it's just a copy and paste out of the history.

Um, it means it can delete data from the host application. As you've said "Jira" we can talk in Jira terms - it is likely that the app wants to be able to delete attachments on issues, but it could also be asking for permission to delete issues or even projects.

* Status and resolution are two totally different things. Which one are you talking about? * Usually, click "link issue" and give the page location when answering "what do you want to link to?"

Jira doesn't log that (it's pretty much irrelevant data, I can't think of any real use for it that I couldn't use the actual creation date for). You would need to change Jira's core code to enable it to record and store it, and that's not something you can do on a Cloud service. You could raise a feature request for…

That's a very different thing to being able to trash other people's projects because you feel yours is wrong. I actually happily support the idea of project admins being able to select their own schemes. Except that in the case of permissions (and some other schemes), you don't need it. A properly designed permission…

Ok. There's not a lot else we can tell you here. You've given us nothing to work with.

There isn't anything more to creating a burndown chart than clicking on the link to the burndown chart display. If something seems "off", then either your data is wrong, or you are not quite understanding the chart or the data. We can try to help you with that, but we'll need to know what you are expecting to see and what…

I am not sure what you are trying to achieve here, but the table with empty cells suggests your script is not presenting any data to go into the cells, probably because it is failing to read it (that's the usual culprit behind an empty result). I can't really help without a better understanding of what you are trying to do…

They come from the priority of the issue.

Yep, I use "watcher = currentuser() and resolution is empty" on Jira.atlassian.com If it's not logged there, there's no point in talking about it - Atlassian don't know about it or have said it is not going to change.

Installing a new Jira is not the answer. Your Bitbucket was set up to look at a Jira for its users, you need to tell it to use that Jira, and make that Jira available to it, not install things in different places. I think you should step back, and review all your accounts access.

It is what you answered, yes. I tried to suggest some ways to work around the broken way the questioners were working, but my suggestions all fit within your original answer (I hope. If they do not, then I've explained it badly)

>We are deliberately separating the UI/UX and Dev Subtasks into separate Sprints to manage blocking dependencies Ok, that's "wrong". A story is something that should be possible to complete within a sprint, completed by the same team. This sounds like you have two teams working on the story independently. As a sprint…

Oh, ManageEngine is not one I have worked with before, so yes, my third instinct is to look at the export options. The second is to see if any of the ME docs mention Jira (or Jira docs mention ME, but all I've found there is "what can it export that we could read") First instinct is to poke people like @Liam Green who I…

No problem - move is an option in the issue actions menu. If you hit it, it will ask you for the target project and issue type. To use it, you must have permission in the source project for "move issue" and "create issue" in the target. Jira looks at the issue id to try to connect emails to their originating issue. It also…

Bulk-<actions> respect the permissions for the projects. My guess is that you do not have "create issue" in the target project. (I think you have "move issue", otherwise bulk-edit would not offer it to you). Note - good thought about company/team projects - I do not know if that permission applies the same to…

No, being finicky about language here, I would say that there are no database converters left. Even the old plugins (apps) which were able to directly connect to another system's database and hoover the data out into a Jira format were far better described as "Importers" rather than "database converters" But, yes, there…

The usual problem with updating multi-something fields is that it is not obvious what to put into them. They contain a collection (array, set, list, whatever) of items as a single value. So we often find people saying "I put 'red' into my colour field, but it wiped all the other values" or "I can't put 'red' into the…

Yes, this is exactly one of the reasons you should not be looking in the database. Empty fields do not have any data, and you can't use SQL to find something that is not there. You can find them with JQL, and all the functions in the UI and REST, because it understands the database via its code. You can't find them with…

It was a bit like a more chilli, less sweet and less smoky barbeque flavour. I can't speak for how squirrelly it might have been, I don't remember ever trying squirrel, despite all the "lovely bit of squirrel" jokes in "Friday night dinner"

I'm afraid you'll just have to count the lines to get a count of the spaces the current account can see. "Downloading" spaces is done by going to space admin -> export - that will give you a file to download containing the whole space.

It's hard to say without knowing which reports you are looking at and what your management team want from "reports". Not too worried about the first part of that question, but could you give us some detail on what your management team are looking for?

I can't see a way to do this with out-of-the-box functions, but I do have a way to stop the problem for new cases. Stop deleting issues. (It's probably the wrong thing to do anyway, as it's disconnecting the customer and it's impossible to get them back, but that's not what we're here for) Create a new project called…

Just as a quick note - the "put a DC licence on a Server and it's a node" upgrade only really applies for Jira 8.3 and above (from memory, version might not be quite right. If you're on 8.5+ though, you're definitely fine, I flipped an 8.5 the other day with just a licence change).

I did try the squirrel flavour on the cat, in the hope she might stop bringing back the real item. I don't think she liked the "cajun", sadly.

By the way, most of the crisp "innovation" here in the UK is done by "Walkers", by far our most popular crisp maker. They're from just up the road for me, founded in Leicester shortly after WW2, but they were bought by Frito-lay while I was at school, and branded Lays in the US (hence the remarkably similar range and…