Nic Brough -Adaptavist- Expert

I think you're questioning the reasoning behind "move issue" needing to go through asking you a whole pile of questions. Moving an issue is changing its fundamental structure. The unique key may change, the fields, the worklows, how it works in front of the users. It simply cannot be a simple process of just moving it. An…

No, that's the point - an issue should be dealt with in a sprint, you don't micromanage it down to when it's going to get done in the sprint, that's up to the team. You can only assume "they said they'd do it in sprint X", so the start/end date is drawn from the sprint plan. And the bit I didn't see last year - " Scrum has…

You'll note that in all those applications, the changes are applied to the structure, not the content of the pages. It's stuff that would be done better in the Confluence theme for the space, not the content. Plus you'll note the point about "how the heck do we apply this to content that the users have completely changed…

There can be data loss, it depends on the configuration. Your system fields and functions are mostly safe, custom fields possibly not. Summary, description, history, comments, attachments - all fine. The four places you will or may lose data are: * Issue type: If the list of issue types available to a project differ, you…

I'm sorry I came across rude, it was not intended that way. I apologise if I've caused any offence. But the schoolmaster bit is still right. You need to stop looking at the database, because it's a mess and you're going to be spending weeks trying to work out a query that probably won't give you the right answer. Links are…

It's worth a quick look at the tables that are "extra" - they should all start with AO_xxxxxx if they are from apps and plugins! You can use the xxxxxx in there to look them up if you need to, but it's probably easier to look through the plugins you've got installed on the source system!

First, simplify a little bit. Forget Jira Service Management - you should look at Jira Software, get that upgraded, and then Jira will select and upgrade the JSM application to the best version for your Software version! I would make three recommendations here: * Go for the latest version of each - more functions, fewer…

This is one of the reasons you should be looking at the XML export/import. The extra tables in your Oracle schema could be because Oracle databases for Jira are structured differently to Jira ones, and you'll have to work out how to change the data you are importing, or they've been created by an app, in which case you…

I rated 1 and 3 equally I think. 2 felt a little weak on the monsters, and although 4 did much better on the monsters (and the story twists), it felt like three fragmented stories, only two of which joined up sensibly in the last few episodes. Love Eddie's character in S4, he was Very Metal, like Vyvyan. And the howling…

Um, you said you are creating issues with the REST API. You use that to read them as well.

Jira is not intended to be run in an iframe, you'd have to build bits of Jira's supporting javascript into the site you are putting the iframe in.

Yes, it's just the converted data. Converting the structure often doesn't work properly, it's far better to let Jira get the structure right and then import.

Go to the project, click project admin, then channels, then portal.

Thanks for checking that @Heather Ronnebeck - I had not thought of that! With original estimate set as the sprint estimate, then I have a feeling this is still correct, but I can't be sure given the data you've given us. The problem is that you're looking at remaining estimate, which the burndown does not. I can fill in…

All releases of Atlassian software in the main downloads are "stable". It is not a useful concept to discuss when trying to work out what version you would like. (The closest I would get to seeing it as a useful term is that you could argue the Early Access releases are less stable, because you should never use them for…

All wireshark is telling us is that it can reach and talk to the other end. It's not telling us that your connection settings are right or why Azure Data Factory isn't reading the data.

Your first query is malformed and although I can see where, I can't see what it is supposed to be doing. The second query in there is probably working. I'd guess the three issues in the first half of the bracketed query do not have any linked issues.

The design decision is right when you have a thorough understanding of how scrum works, but team-managed projects are definitely the problem here - as you say, they lack the flexibility to define your columns properly.

Welcome to the Atlassian Community! You will need to talk to your administrators, asking them for access to the board. We are a community of people here to talk about Atlassian, and although we can talk to you about problems in general, we are not your admins!

You could blank it out in the create screen with a Behaviour from the Scriptrunner app (Yes, I know, a blatant advert for one of my own companies apps, but I am not aware of any other apps that could do it)

Assuming by "get", you mean "read the issue over the REST API", then all you need to do is read the issue, the response will contain all the fields, including the status.

No, an Epic is a container for stories, not an attribute

Welcome to the Atlassian Community! The screen looks like you are in team-managed project. These can only have three layers - Epic, Sub-task and Issue. You only add issue types at the issue level.

First go to the project and look at the administration. Find the "permission scheme" in there and read what it says for "Create issue" and "Browse project". It is likely to say things like "Role: users", "Group: any logged in user", "Group: Thingy", or possibly combinations of many. If it says "Role: something", then you…

Do not do that. It is unlikely that your "clean up" and "migrate schema" will leave you with a working Postgres database. Once you've got a working (but very empty) Postgres database, you should empty out all the tables and then import the data from the Oracle data - just the data.

Yes, it does. Are you going to the portal via the project admin?

Welcome to the Atlassian Community! The reporter field is populated with the Jira users who have the permission to create issues in the current project.

As I said, you'll need to convert it by hand if your tool can't do it.

Your second query is the better way to do it, it will return all issues in the project that are not in one of those two status.

Yes. You can migrate before your licence ends. You say " It is also not possible to migrate to the cloud or to the Data Center version before the date of termination of support due to restrictions." - that's complete nonsense. It sounds like someone has not understood what a migration is or how software works and handed…