Nic Brough -Adaptavist- Expert

I suspect your virtual machine is going through a proxy which is configured to block this access. (It's not a Confluence problem - as you say Confluence works when accessed from other places)

Yep, you can use automation inside that single project to do this. Go to the project, hit project settings at the bottom left, and then find the link to automation. Add one that triggers when you need it (issue create is easiest) and then chain a few "issue creation" blocks off it.

No, it is not possible to do that. Board admins can administrate their whole board, and admins can create whatever boards they want.

I covered that in my original answer, and first comment.

I would not risk that. You should do merges/migrations one at a time, because you're going to have to do conflict resolution on every migration, and running at the same time means you can't reliably do that. Let one migration finish, then do one set of conflict resolutions and import the second batch. By the way, you can't…

Reporting outside the boards is a little different. Most of Jira looks to the resolution field for "done". If the field is empty, an issue is not done. If the field is filled (with any text, including "unresolved"), then the issue is done. I suspect you're setting a resolution as your issues go into "done", but not when…

Welcome to the Atlassian Community! This isn't really a Bitbucket question, it's more about what your Server is doing at start up. To get started on an answer, what operating system are you running Bitbucket on? (We need to know what the system startup control system is LSB, Systemd, Sys V, Windows, etc)

It's pretty clear that this is a permissions issue in the database. Could you try re-running GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO jira_user; after the import (and also check that Jira is definitely using jira_user for access - look at Jira-home/dbconfig.xml 

I think the notification scheme is probably working fine, but you've not made the changes you think you need to the one that is causing you problems. First pick an email you didn't want to get. Look at the project that is named in the email, in the issue key. Now look at the project's notification scheme. Each line in a…

The anti-spam bots don't like the content. I've pulled this one, and the one you're referring to, out of the spam bucket - this should help the bots to not over-react on your next postings!

Welcome to the Atlassian Community! Issues that roll over into the next sprint when they're not completed don't actually "move", and they retain the data that they were in the old sprint. Jira doesn't have any functions to find it, so you have to do this manually, creating or changing filters to match the current sprints,…

Welcome to the Atlassian Community! "Visible under to-do" is a bit too vague to be sure, but it usually means one of two things: * It's in the to-do column on the board. This probably isn't the case here, as you mention the status is set to "done", and I imagine you have that mapped into the last column on the board. *…

@Nate Gallaher Ah, now that is a bug. But you didn't describe that before, so I had no option but to assume that the message is coming from a misconfigured board. (Not sure why you'd want to be searching for the board you're already on, but it shouldn't be popping a misconfiguration error) @Amman Habib no, it's nothing to…

Yes, that's correct. Your filters look absolutely fine to me, they're not the source of your problem. I think we need a look at the sub-task itself. I'd like to see the structural stuff - status, resolution, breadcrumbs, issue type, dates, if the versions fields appear on it at all, but not the content of the summary or…

There are a few ways to do this, but all of them need apps and a little scripting/coding. Do you have Automation, Scriptrunner, JMWE, Powerscripts etc? If you've got more than one, any preference? (If you want answers from me, then I won't be able to help you with JMWE or Powerscripts, I've focussed on the first two…

There is some control over it, but for Jira Service Management projects, there may be two types of email you are questioning (Actually four, but two of them are about users sending email to Jira, so we'll forget them) Is this about customers who get emails about their requests via the JSM "email channel", or the back-end…

Welcome to the Atlassian Community! I'm afraid all we can do is tell you to do what you've already done (go here, click on transfer, answer the questions). You've landed on this error message because the organisations are not set up in a way that allows you to do it. You need Atlassian to fix this on their side, which is…

Your backlog is actually a different view of your board, and works off the same filter. So, what you could do is alter the board filter. Instead of "Project = X order by rank", use "Project = X and status not in (<the status before backlog>) order by rank" There may be other ways to do this, but it's the simplest one for…

Ah, Carlos beat me to the rest of what I wanted to add.

>is it possible to join the instances and the charge be proportional No, you can only run a system on one plan at a time. You'll be able to link them together technically, so they can work together, but they will still be two separate systems, with two separate plans.

The quick filter's do not matter here. It is the "sub fitter" on the general board config, below the board fitter we need to check

You should import your stories (and bugs and tasks) at the same issue level as features.

Ok, well >We added few custom issue types and "Features" is one of it which sits between "Epic" and "Stories". You can't do that. You say you are importing features as a child of epic, which means they are at the base issue level, alongside stories, tasks and bugs. Epic name field is a bit of a kludge for Epic, so yes, I'm…

Welcome to the Atlassian Community! What do you mean by "permissions change"? Is the permission scheme for the project being changed?

Jira can't create sub-tasks from email. You'd need to write a new email-handler to do that.

A, ok, What is the error you are getting?

To look at a single issue, without any custom fields, you're looking at 20-30 joins. Don't do it.

That's not what Story points are for, and it's a bad practice to measure individual performance (in fact, illegal in some places). Jira doesn't support reporting like that.

You wouldn't normally create sub-tasks under service requests, but when you do, you should be working with them within the issue. Sub-tasks are not independent items, they are a part of their parent issue. There's no need for them in the queue, they're part of the parent issue (which does go into the queue)

Welcome to the Atlassian Community! The sprint names are a string, but your people have chosen to use simple numbers for them. It's a bad practice to rename sprints, they should really be sticking to a single name with some obvious sequence in them. If you're going to change the sprint names, then there's no "query" for…