Nic Brough -Adaptavist- Expert

I think @Angélica Luz beat us to it as usual :-)

Welcome to the Atlassian Community! There are millions of Jira systems out there in the wild, we, as a Community of people here to talk Atlassian, cannot possibly know all of them. We're outsiders to your system. We have less knowledge and less access to your "techjira" than you do. We can tell you that "process area" is…

Actually, this is one of the few times it is ok to use SQL on a Jira database. It is a slog, you still need to be very careful, and it is usually NOT recommended to go the other way, but when some fields are of a certain type, it is possible to "convert" them to another compatible type with a bit of hackery. The rules are:…

Changing the name of a field has no effect on the data it holds on issues. Do you mean that you selected a different field (with a different name) to look at?

You have answered your own question here! "done" is not the last column. "Validated" is the last column, and all the other status in your workflow mean "not done" because they are not in that column (whether in other columns or not mapped, they're not done because they're not in the last column) You'll need to map your…

It is mostly a manual effort, as each case is different. Some parts of a cleanup can be automated or made easier with scripts etc, but status is not one I'd worry about too much, the manual effort in doing it is smaller than trying to automate it. For status (not screens, fields, issue types etc, they can be different,…

If Cloud is out, then DC is your only option. DC and Server are actually the same software, configured very differently. You can run Server and DC nodes on anything you want to (your own real or virtual hardware, Azure, AWS, etc) In more recent versions of the Atlassian applications, Atlassian have made it a lot easier to…

I'm afraid not. We'd need to add a "language pack" for any new language, and that can only be done by Atlassian for Cloud (admins can add them to server/dc). It's definitely something there should be a request for. https://jira.atlassian.com/issues/?jql=text%20~%20albanian is all I can find on the subject, and none of it…

What do you mean by "my assigned view"? Views do not appear on boards, I am guessing you might mean "issue" - as in "There is an issue assigned to me that I expect to see on a board, but it is not there" Could you expand on or explain your question a little more please?

Um, why? I get the same error. I expect it - I've never been asked to use that site, so I don't think any admins have ever added me. I don't think it needs Atlassian support, just question the owner/admins of the site.

We can't help with a problem that has not been defined. Please give us something to work with.

So not sub-types of resolution, you just mean someone (or a preset function) has put a resolution you don't want on an issue when it was closed (meaning the status changed to closed) You'll need to re-open the issue and re-close it, going through the screen that asks for you to set a resolution, and select "rejected"…

They are relevant, when you're looking at the story of which they are part. Sub-tasks are not relevant to a sprint, they are not sprintable items, they are a part of their parent story. It's nonsense to do sprint or velocity reporting on them as anything other than as a part of the story.

>Why only stories in Jira can be estimited by storypoints, other types of tasks including bugs, tasks, subtasks are not? Have a think about what Scrum is for and what the estimates do. Velocity is a measure of delivery against commitment. At the beginning of a sprint, you commit to delivering a set of stories and you are…

There is a version of the automation app for DC, that's probably the first thing to try!

Not sure why you commented on an unrelated, 3 year old, question there, but hey. This is exactly what it says it is. Your licence ended in 2019, well before the release of Jira 8.1, and the licence only entitles you to use versions released up until the end of the licence time. What you should do is: * Install a new…

You'd need to get the app re-written so that it pops a dialog instead of opening a new window/tab. Probably need to raise this as an improvement request with the vendors.

The steps for upgrading are given in the documentation you have linked to, Instead of asking us for exact "steps to upgrade" that we can't possibly give you because we do not have your installation in front of us, can you tell us where you are stuck? What are you not understanding in the docs? Or what is going wrong? Or…

I also mean the installed macros. When you do a full backup and restore as you suggest you have, user macros are included in that. So, could you tell us exactly what you did to do this migration and upgrade?

There is no gadget for this built-in. Check out the marketplace for reporting and gadget apps that might add one.

This is exactly what it says it is. The account you are using (with <myemail>) has not been added to the list of accounts that can use Confluence. Check with the site admins that it is in the "can use Confluence" group(s) or role(s)

If the version of Confluence is not changing, then yes, you can safely do this. As well as the database, you'll need to consider * Attachments (physical files under the attachments directory in the home directory) * The index - yes, run a full re-index immediately after restarting Caches, temporary files, locks and so-on -…

Ok, you need to be clear on what a sub-task is - it is a part of its parent issue, not an issue its own right. They do not appear in sprint reports because they are not sprintable items, they are irrelevant. The sprint items are the stories you commit too, not fragments (sub-tasks) of a story. The cumulative flow charts do…

See https://community.atlassian.com/t5/Sourcetree-questions/Cylance-virus-scan-issue/qaq-p/1471827

Sorry, try "issue statistics"

What do you mean "getting different url"? What have you done that presents a single portal on two urls (Cloud doesn't do that itself)

No, the DCs are Ireland and Frankfurt for Europe.

The validators in Cloud were very limited until relatively recently (I think there were only two available!), that's probably what people were working from when they told you that before. Now, we can script/automate/add-on plenty of them, so it's no longer true.

A full backup and restore will retain all user macros, so I suspect that's not quite what you have tried here. I notice that you're trying to do a move AND an upgrade at the same time. Could you separate these two out and tell us exactly which one you are trying to do first?

Start with a run through of https://confluence.atlassian.com/jirakb/bundled-plugin-not-available-error-thrown-on-jira-server-login-212173447.html