Nic Brough -Adaptavist- Expert

Jira Data Center does have Advanced Roadmaps, yes. I won't bother to answer for server - you can't get new licences for that anymore, and you don't want to bother installing it.

You can't change a company-managed project to a team-managed one, or vice versa. Closest you can get is to create a new project and move all the issues from the old project to the new one (there may be some data loss as custom fields work differently between the two types)

Welcome to the Community! You could connect the two systems with an Application link, which would make them aware of each other and provide easy linking between issues on the two systems, but all you will be able to do is link issues (refer to issues in the other system) Because the two systems are separate, you won't be…

Confluence isn't a document store, it's a wiki. Generally the best approach to getting other documents into it is to import them as pages, not attach monolithic files Confluence won't really work with. Confluence can cope with lots of attachments, that won't be a problem for it, just clunky to use. (It can struggle with…

It is not going to be available any time soon. You will need to change the keys of your projects to valid patterns before migrating them over to Cloud.

So we need to look at why your search for "epic name =" does not find this Epic.

As I said before, you will need to pay the licence fee for Oracle Java. See https://community.atlassian.com/t5/Jira-questions/Price-upgrade-for-oracle-JDK-in-2019/qaq-p/914167 https://community.atlassian.com/t5/Jira-discussions/Java-11-and-OpenJDK-support-for-Atlassian-Server-amp-Data-Center/td-p/872998 Atlassian's…

I am not familiar with foxwiki and typing it into a search engine does not help - the first hit I get that makes any sense is a wiki running on Moin Moin. But there's no guarantee that this is the wiki you are talking about. Could you tell us what the engine running this foxwiki is? There's another problem too - I'm…

Well, actually no, although the tier is 10, Cloud pricing is more flexible at the low end and will only charge you for the users you have active, so you should find it's running at $5.50

Welcome to the Community! Screens do not have anything to say about fields being mandatory. You have two routes to make this work - either make the field optional in the field configuration (not the screen), or have the automation set your "tag" field.

It is the only option for this use case. Why would it be a non-starter? I am curious as to what you are trying to achieve here, in that what would stop you from getting a starter licence so you can have an author and a worldwide audience for them?

What do you mean by "plan upgrade"? Do you mean you are trying to upgrade the software, or upgrade the number of people you have using it?

Welcome to the Community! This message does mean what it says - your Bitbucket is protected by SSL and you have not given the connection the certificate or credentials that tell it that you have the right to clone the repository. Or the repository does not exist.

But when you search for that Epic name, nothing appears (for Epic name or in Epic links) because you don't have an Epic with that name. Your screenshot is of the Epic's summary, not its name, could you check the fields in the right hand bar for the actual name of the Epic?

Welcome to the Community! You have not said what your "tasks" are exactly - are they issue level types or are they sub-tasks? If they are sub-tasks, then they are part of their parent story and not things you measure velocity against, because you don't commit to doing them in your sprint, you only commit to delivery of…

You can't do this with scriptrunner or any other customisation tool. You would need to write an entirely new field to handle it. What you have defined here is a variant cascading-select, where instead of the first half of the field being a select list option, it is an issue picker. You can do those, there are apps that…

Welcome to the Atlassian Community! I think that you may be in the wrong place though - Atlassian doesn't have "plans" with those names.

You're not running an upgrade there, you have run a new installation of your system.

It is indeed 10 - that's a starter licence.

Welcome to the Community! There is nothing like this in Jira Server, you have to be an admin to do project configuration. Cloud has "team managed projects" which do allow the owner of the project to configure it in many ways (but this of courses loses all the benefits of standardisation across projects)

So, having many sprints across your instance is normal, every team could be doing their own sprint, that's what it is for! I am no longer sure what the actual problem here is - could you explain?

Welcome to the Community. The answer hasn't changed - yes you can do this. However you approach it, you should look at the core things you need to do to build a Jira server: * Install a Jira system * Configure the server/node settings in the settings file(s) * Give it a connection to a restored copy of the database, and…

Um, sorry to repeat it, but sprints do not belong to projects. You need to look at your boards, the places that sprints are defined.

Exactly, that's why I would never bother putting resolution on the create screen, it's a tiny edge case and can be dealt with by "click on resolve immediately after creating it", rather than having to set up a whole new issue type and matching workflow. I too am intrigued as to why there is a special note in the…

The only case I can think of for setting a resolution on creating the issue is for retrospective reporting (this thing happened, we fixed it before raising an issue, but we should raise one to report on it/log time against/etc) And for the sake of simplicity, most of us never do that - we create the story and then just…

>"But how can that be the default value of the stories I create?" It should not be, that's the point. In Kanban, you set a fix version on issues when you know what version it's going to be fixed in. Then you release the version (which takes the issues off the board)

Kanban needs a way to say "this issue is done and no longer needs to be shown on the board". The default for Jira is to assume that an issue that is in a version that has been released is done and can be dropped off the board. That's why it has a "release" button at the top of the done column which tags all the done issues…

Your Confluence is not installed correctly, but there's all sorts of things that could be wrong with it. Work through https://confluence.atlassian.com/confkb/confluence-does-not-start-due-to-spring-application-context-has-not-been-set-218278311.html to find the error (I know the doc is about Confluence not starting, but it…

You could use a label or custom field to contain the information about re-occurrence.

Welcome to the Community! There's a lot of things wrong here, and there's no direct and simple answer because of that. * Post-functions are for doing something (usually updating data somewhere) when someone transitions an issue from one status to another. They have nothing to do with the display of an issue. *…