Nic Brough -Adaptavist- Expert

OK, good, I can see that. The way you were writing earlier gave me the impression that you were not understanding what it was doing (that ADF functions and docs are not telling you that all this stuff about tables and objects are entirely ADF things, nothing to do with Jira), but your last comment clearly shows that I have…

You would need to do that anyway! The component "Penguin" in project A is not the same thing as the component "Penguin" in project B. Moving issues from one project to another will always lose the components on it because the components are project aretifacts.

This does not look like you are following the documentation. The loss of macros is screaming that you're not doing a migration or upgrade at all, and I really cannot work out from this what you are actually doing.

I am very confused here, you talk about consecutive sprints in the same sentence as parallel sprints - these are the opposite of each other. Do you mean "concurrent" instead of "consecutive"? Either way, we can answer most of the questions, as it doesn't matter which way you're working with sprints. Yes, use the board…

Depends on the board you are using. Most boards have a configuration for columns that allow you to map many status into one column. (Again, the colour is utterly irrelevant, it is only the last column on the board that matters) Some do not - with those non-mapping boards, yes you are stuck, you have to have one single…

So instead of setting up an Atlassian account based on the old user name, you chose to create a new one. That's fine, but it does mean Trello now sees you as two separate accounts. You'll need to get the old account set up as an Atlassian account and give it full permissions, or get everything transferred to the new one.…

The components are listed for each project independently, they are purely project artifacts. There are a couple of tricks you could play (scraping the list from the admin screen, converting it to csv and importing some dummy issues in the target project, for example), but it will be simply duplicating the names as a new…

The colour is irrelevant. All that matters is whether an issue is "done" or not. Jira's boards define the last column as done, so for something to be done, it needs to be in a status that is in the last column on the board. You need to map your done, rejected and outdated status into the last column on the board

Ok, that's not quite what I was hoping for, but let me explain why. All too often, we hear "I just copied and pasted the licence" and find out that is a huge oversimplification, and actually the cause of the problem. What I am hoping you are doing is: * In a compliant-standard browser, open my.atlassian.com and go to the…

Welcome to the Atlassian Community! If you have Trello gold (or any other paid Trello) it will not offer you any trials, it will just, well, work. Could you have started looking at another Trello system, one that you've not yet taken ownership of (and paid for)? Or have you shut down your gold subscription? (you'll be…

Welcome to the Atlassian Community! I think you've run into a quirk in the language in the code, rather than a direct conflict. The pre-upgrade check is trying to tell you that your current version of Postgres is not supported on your current version of Confluence. (In my experience, all Confluence 7s work absolutely fine…

It is not, sorry, people expect it to work (roughly) the way it does, and not be restricted, so there's no functions to limit it.

I'm afraid asking for votes is not going to do much. I am not saying you should not, I just don't want you to think no-one has seen what you're asking. People will tend to reserve their votes for things that affect them more though. For what it's worth, it's not JIRA either - Jira (note the trademark/name changed case a…

Only humans (with admin rights) can change that setting. Although it is very easy to accidentally reset while you're in that screen. You'll need to talk to your other admins and ask them not to mess with it (or at least check the setting before they confirm any changes in there)

Ok, there's not a lot to go on there. There should be more of an error message, but if not, we'll need to know the *exact* steps you have gone through: how have you taken the key from your atlassian account through to the confluence licence page?

Ok, great, that covers everything, thank you! You are a "Jira Admin", not a "System Admin", and only system admins can add apps to Server systems.

It's nonsense in Scrum. You don't take bits of a story between sprints. It might well work for your team, but that does mean you're not doing Scrum and will need to recognise that a Scrum tool such as Jira is for Scrum and so is unlikely to be that helpful for non-Scrum process.

That would be nonsense, as a sub-task is part of its parent. Technically, sub-tasks don't even go into sprints, we just treat them as such because they are a part of their parent. But, yes, you can split them - by moving them to different parent issues so they can be part of things that do go into different sprints.

Can you show us what you see on the admin -> manage apps page where the upload link should be?

Welcome to the Atlassian Community! We're a community of people here to talk Atlassian, we're not support. But we do try to help. How were you preparing this report on your old server system?

Have you downloaded a Server app and are trying to upload it to a Cloud system? If you are on a Server or DC system, are you logged in as an administrator?

You need to add a transition screen to it (and probably all the ones that go into resolved or closed)

Software projects do not have requests in front of the issues, but when you move an issue from JSM to JS, it does not delete the data that a request was there. Your instinct is correct, you would need to export and import (because that will lose all the request data that is confusing your JS)

I think you're missing the point here. There is nothing built into Jira to support this. It has a REST API, that's what ADF is using (there's nothing else it can talk to Jira with). The REST API has nothing to do with tables, jiraobjects and the rest. It returns the data remote systems ask it to (or does things they ask it…

See https://community.atlassian.com/t5/Jira-Software-questions/Not-work-link-for-documentation-about-Insight-RESt-API/qaq-p/1795302 for an update on that!

No, it does not, not in terms of the sprint. Again, you commit to doing a whole story, not bits of it. That's what all the sprint reports are looking at - commitment vs delivery. Sub-tasks certainly are deliverable. They're a deliverable part of a story. If you want to look at them and measure their progress, that's fine,…

Non-Agents can have some interactions with service management requests/issues, viewing, commenting on etc, but it's the job of the Agent to look after the process, not other users. So, no, there's no way to do this off-the-shelf. You can rig some stuff up via Automation or scripting, but that all relies heavily on spawned…

And that's pretty much my whole point. There is no SQL access to Jira Cloud. There are no "tables" to look at, certainly nothing that supports "select * from <table>". The connector is using the REST API to get some data, but it's not a table, and it's not using SQL. Whatever you're thinking of as a "table" in here, it is…

Projects. Versions belong to projects. Boards are a view of a set of issues, they just show any/all versions that happen to be on the issues they are showing you.

Ah, it's ok @Andy Heinzer got it - he might not be an admin or owner, but he at least knows who the owners are. And what it's for, so he's asked a better clarification question!