Nic Brough -Adaptavist- Expert

I think you will need to explain this a bit further. A Jira "create issue" form, is, well, a form.

It will react correctly, a 300,000 issue project is not a problem for Jira. You will need to think about how your people work with it though.

A cache is a way of making thing work faster by way of making data available faster because you have it to hand. Imagine a typical English speaker (as a first language). We tend to have about 20,000 words to hand, and grasp instantly another 20,000 with a bit of thought. (There's an essay about the smug gits who do…

It's fully supported. The error message you're getting appears to be a fault with your settings. See https://community.atlassian.com/t5/Crowd-questions/Samba-Ad-Dc-Connector-Problem/qaq-p/1436163?utm_campaign=immediate_general_question&utm_content=topic&utm_medium=email&utm_source=atlcomm

The free and starter ($10) subscriptions do not have direct support included (it costs a lot more than $10 to do any level of support). Atlassian simply refer the unsupported people to public resources, such as the community here. We can try to help you, but we're still not support. Whatever you need support on, we're sort…

We use organisations for that - https://support.atlassian.com/jira-service-desk-cloud/docs/add-an-organization-to-a-service-desk-project/

The backlog and the board show the data from the statistic field you have chosen for your estimates. From your question, it sounded like you have chosen one field, but are then putting your estimates and time tracking into another. I have probably completely misunderstood what you are doing. Ignore the time tracking for…

You need to use which ever one suits you better. We can't tell you which option you want to use.

Jira is not a service architected for chat. I'm not aware of any app that would insert itself inside Jira just to expose a Slack (or other) client as part of it.

Yes, it can. Could you explain what you are asking about?

You can use admin -> backup to get a download of everything. That can then be uploaded into a new Cloud system or imported into a server system to replicate what you have in the old system

Yes, projects have a single permission scheme. I'm not sure what you are looking for when you ask about using a permission scheme. They are reasonably simple - they are effectively a list of things you might want to do to an issue alongside a set of rules that identify who is allowed to do them (for example - log work:…

The best way to migrate a space from one Confluence to another is a simple export space, import space cycle. You don't need the source and target to be close in versions or underlying tech You can export from server, cloud, or dc and import into any of those three irrespective of source. You can export from 4.x and have a…

There is no REST call to do this (yet). You can see what you can do over at https://developer.atlassian.com/cloud/jira/software/rest/intro/

You have set your maximum "heap" size for the java virtual machine higher than your server actually has the memory for. You should set your maximum heap to at least 1Gb lower than the physical memory of the server (unless you're using an optimised or lightweight operating system, you should be allowing at least 1Gb for…

There are open requests for sorting and "quick filter" like functions on the bulk-edit selection screen. I think those would help us a lot, and last time I remember seeing them, Atlassian had them in a "we'd like to do this" status

We regularly recommend: * Jira Align if you're well over 500 users and are going to end up with more than a couple of release train type things * Advanced Roadmaps (Portfolio) if you're willing to do things the way it expects you to - it's less close to SAFe than just doing Jira with a lot of projects, but does enable…

Yes, assuming your "task" issue type is a standard type (not an Epic or a sub-task type)

You can start each node separately, no need to look at the others. (That's one of the points of having a cluster - the nodes work together, but are independent of each other)

No, the service can only have one type of licence. You're not upgrading people, you're upgrading the whole service.

You'll need to explain what an AIT Task is and what you are configuring - we can't tell you about your setup!

I don't understand what you mean by "locks"? What is the behaviour of a "locked board"? What appears to be happening here is that you're building a search that doesn't have "order by rank" on it and then correcting it later.

You need to log in as an administrator - to get that, you'll need to get an existing administrator to add you into the group that says you are an admin.

The application log is in <confluence data>/logs/ - look for atlassian-confluence.log, but have a read of all the others in there

Jira doesn't do field level security, you either offer the field or you do not

Ok, nothing to do with categories then. You may be able to simply edit the issue to change the issue type - this is only possible if the source and target issue types share the same configuration. If you cannot directly edit the issue type, then use "move" - it will offer you project and issue type. Change only the issue…

Slack is one of the main ways Atlassian now does notifications. Atlassian and Slack have been significant partners since Atlassian gave the IP for hipchat and stride to Slack. I think you might want to have a looks at that.

Estimate, plan, burn down/up in story points. Log time worked in the time-tracking fields. Time and estimation are totally separate concepts. Most humans instinctively understand time estimate and spent, but it doesn't really work for complex tasks, which is why we move to things like story points. (Example - I could put…

I really like editors that do syntax highlighting (except emacs - it does it, but I don't have any inclination to learn the damn thing, I'd rather go get another degree, it'll be easier and faster). I would have said I love them, but I can't quite go that far when the reason I like them is that they highlight the facts…

I am sorry, I have again failed to understand. We do not usually see status as being task or story, those are usually issue types. A status is an indicator of where an issue, task or story (or other issue type) is in its process. I'd expect to see status like "open", "in development", "doing", "done", "cancelled", "with…