Nic Brough -Adaptavist- Expert

What do you mean by "can not map the status"? You're absolutely right that this is a critical item (it's not technically a field, but that's not important here). You need to give it a status, unless you are in the one place where it's ok for every imported issue to go into new/open/to-do - whatever "create issue" would do…

Sprints do not belong to projects, they are separate individual entities, like issues are. It's not "closing a sprint of another project", it's closing a sprint. One that happens to be across projects and boards.

"Permanent" is not quite the same as "Perpetual". The Perptual licence you bought lets you use any version of Jira that was released before the end of the licence. So you can always get to your data and run an accessible Jira system. But it does not cover maintenance, one part of which is "later versions". So to move to…

Correct, the Java API is internal, your code that uses that would be running inside a server. REST is the external interface. It is provided by internal code though, so there's some commonality there.

No. Versions are project artefacts

No, because there is no adjustment. If someone needs to log an hour, while the next one needs to log a half, then they should log 1h and 30m respectively.

It's not mandatory to have 500+ users, but it almost certainly will be uneconomic for you.

This is one of the symptoms of having the wrong permissions on the installation and/or data directories. Could you stop your Jira, make sure your install and data directories for Jira are all owned by the jira account that is going to run it, and then restarrt it?

Yep - enough for them to be considered a "staple" in every food shop in the UK, Spain and India.

Sorry, We have no access to that.

When you click "edit filter query", it should take you to the issue navigator which shows you a paginated list of the issues. At the top of that, it'll tell you how many there are.

You can add those custom fields to the screens used for the sub-tasks. (Remember that "group assignee" is not assignee - you rightly cannot assign groups, just indicate them alongside the actual assignee)

It is included in your commercial licence.

No. This will not work the way you would like it to. But, there is a far better option. You can create a standby for production Jira using your "development" licence. This matches your production licence (250 users), and has several uses, including backup/failover/standby servers. Go to your "my.atlassian" account, find…

This is often what it says - the heap is too small for something in your Confluence and you need to give it more memory. However, there's also a db error in there, and sometimes those can cause loops which then cause memory leaks, leading to the heap space error. What are the database settings in confluence.cfg.xml in the…

That server.xml is defining three connectors on the same port. It looks like Tomcat accepts that, but only runs the first one, which is not correctly configured for your proxy. You need to comment out the first and second connector in your file (starting at lines 10 and 28 respectively), and let it use the correct one…

When you click update filter, is should take you to the issue navigator where you can adjust the filter so that it doesn't try to include too many issues. What does the filter show you? There's a summary count on the issue navigator page.

You'll need to ask the person or team that asked for it. I would guess someone is using Jira to track risks, as you can "mitigate" a risk.

* See https://confluence.atlassian.com/conf63/supported-platforms-929730053.html * See https://confluence.atlassian.com/conf69/migrating-to-another-database-950285442.html

To hide a project, remove the permission that gives people access to it. Check what roles and groups "browse project" is granted to in the project permission scheme.

Run through https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html as that covers the issues you may run into. One thing it doesn't emphasise that I would like to is that you should skim the release notes for each intermediate version - I say skim because issues and warnings will jump…

What does the document say?

You can use it with Cloud (any version), but you'll need to go via Atlassian Access, which does not have a free option.

You might want to try reaching out to a partner instead.

Could you tell us what type of field the "Aha! Rank" is shown as in the list of custom fields, and explain what is wrong with the ordering? "It does not work" does not give us any information

See https://confluence.atlassian.com/adminjiraserver0713/supported-platforms-964983071.html

See https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html Bear in mind that you need to go through several versions. The recommended upgrade path is 6.3 -> 6.4 -> 7.0 -> 7.13 -> 8.9 You might be able to skip 6.4 but under no circumstances skip 7.0. If you skip it, it will corrupt…

What do you mean by "qm format"? Repeating something meaningless does not explain it.

What do you mean by "qm code"?

Have a look at the field "context" when adding a custom field. That allows you to have different field settings by project and issue type.