Nic Brough -Adaptavist- Expert

It's probably going to be the same answer - look at all the issues the error report is listing, look at all of their subtasks, and check that they are all a) On the board in the current sprint b) All in the last column on the board You are going to find at least one of them does not match those two criteria.

It is not, Jira does not have field-level security or permissions. You could move the field edit into the workflow (so that people can only change the content of fields during a transition, and you can protect transitions with conditions like "must be in group"), but that can make your workflow messy and it's not obvious…

Ok, in the automations, you've got four types of block you can use - triggers, branches, actions and conditions. I think you should be making use of a condition that looks at the summary field, either with JQL to see if it matches, or directly with a "contains" type statement.

"Done" is the last column on the board the sprint is shown on. The actual status in the column don't matter too much, and their status category (colour) is irrelevant. It's easiest to think of a board as representing a team. "Done" for the team using the board means "this team has no further interest in this story, we're…

Those menu items do not have a "disabled state" display option so I'm still a little confused (if you don't have a working option, it doesn't appear in the menu) What happens if you refresh the page and try again? Or save your current update and come back to it?

There's no way to remove options at that level, you can only do it at a project level.

The cache messages are usually errors falling out as a result of other problems. Your system will go into a setup cycle if the database connection has been damaged or has stopped working. You'll need to check what database settings are in the configuration XML file in Confluence's home (data) directory, and that the…

I don't know how your infrastructure is set up or who owns it, but yes, it's probably the network team who will know what the rules are for URLs for new services, and can allocate you one, then set it up so your DNS can send people to your proxy. Your network team may also provide proxies for you.

Welcome to the Atlassian Community! Summing story points up from sub-tasks is not something Jira does natively (because you don't put sprint estimates like story points on sub-tasks), so when you say "I have story points on subtasks that automatically refresh totally up to the parent ticket.", you or your admins have added…

Welcome to the Atlassian Community! Will what affect it? Please, some context?

Ok, so that's a complete non-starter. You can't run your system on poweruser.jira.com because you don't own it. You could do it within your network, by poisoning your internal DNS servers, but that's a bad practice because you have to remember to maintain it and it masks potentially valid external sites. So, start by…

That's basically a terrible idea. The software is for doing source control, it is not a web server.

Welcome to the Atlassian Community! This is what it says it is. You've already added the key with a different account. You'll need to create a new key for your new account (and stop sharing keys across accounts)

It looks like your previous attempt to upgrade has broken your database. You'll need to restore it from a backup and re-do the upgrades.

How are you serving up poweruser.jira.com? Do you own the domain, or is it hosted for you?

You say you have no access to the email address, so the only thing you can do is stop using it. You'll need to create a new Atlassian account, with an email address you do still own.

You will need to undo the changes your other admin made to the workflow, providing a route to close the issues the workflow is used by.

Ok, so you're trying to run an upgrade. What errors do you see when you run it? It's obviously failing, so the question is actually where it is going wrong. Bear in mind that if it fails after upgrading the database, it will have upgraded the database, so the old version will not work any more. You can't just re-do the…

Again, Why are you trying to run a website in Bitbucket?

We need an explanation of what "not working" means before we can help you.

Ok, you'll need to ask an existing administrator to add you as an admin, or, better, change the permission scheme in your project so that the project administrators have the delete issue permission.

So, again, this happens when you point a new version of Confluence at an older database, rather than running an upgrade. This can be a valid way to upgrade, but it only works for versions that are closely compatible. Could you try upgrading your 7.12 to 7.18 by running the upgrade process instead of creating a new 7.18…

Welcome to the Atlassian Community! I am not quite sure what the problem here is. You add a new issue and it goes to the bottiom of your backlog because that is where it should land, then you re-rank stuff and maybe it moves, what is wrong with that? (Or, more importantly, what part of that process is not working for you?)

Yes, Atlassian is building their tech on top of other things. Almost everyone does. If those things are compromised, then you need those things to be fixed. You can't expect someone else who has built on it to fix it directly, they have no choice but to move on. Atlassian is doing better than most suppliers of software…

Go to trello.com, click "log in" and enter the email address and password you have used for your Atlassian account.

Sprints do not belong to projects, they are linked to boards. Go to a board which has the sprint on it, and end the sprint. That will enable you to move to company-managed projects and boards (and hence parallel sprints)

Yes, this happens when you just point a different Confluence installation at a database from another version. You should upgrade your Confluence, not point a new install at an old database.

Yes, classic was renamed "company managed" a couple of years ago.

Welcome to the Atlassian Community! You will need to ask your administrators to give you the permission to edit sprints.

What search are you running to get to the export-obsolete-list option?