Comments
-
Ok, that's even more simple - you don't have any sub-task types in this project's issue type scheme.
-
It does not matter if it's an upgrade or an install, the new branding and look and feel applies to later versions of Jira, the old stuff is gone. You could install an older version of Jira if the slight changes really bother you that much, but you'll be missing new functions and fixes, and will eventually need to upgrade…
-
I am afraid I cannot read the error messages. To my shame, I only speak English. You should be seeing these errors echoed out into your logs, with more detail though, especially the one in the big pop-up box. Could you check through the logs for those errors and look at what causes them?
-
Add a new custom field for severity, then configure the fields in your kanban project so that they include priority and severity.
-
No, trials are limited only by time. It looks to me like the "new issue view" is the problem here, as it does not contain sub-task creation links like the old view.
-
Vendors of plugins do not change often, are always documented, and the plugins usually provide automatic upgrade paths if they do. Notable ones I remember would be the Jira Suite Utilities going to Beecom, and Adapatavist taking up ScriptRunner, the Kanoah apps, and Project Configurator (Adaptavist kept the people as well…
-
Have you adjusted the space permissions to grant yourself add/edit page?
-
That suggests you've not hooked up the AD correctly to the new server so it can't check the password. The Crowd logs should tell you more about that.
-
Sorry, I was not clear - the layout change is a different topic! We're having problems where people say "new view" and we don't know whether the conversation is about the UI change or the Issue view change.
-
It depends. First, is your "new" installation active, or is it empty, awaiting the data from the old one? If it is empty, then you should be able to take a backup of each system and restore it on the new system (then delete anything you don't want to move). If it's not empty, then you are going to have to engage in…
-
Ah, ok. I would look next at the workflow, as the other place that could be setting an assignee
-
There's a lot of comments about the change of layout - the champions have been trying to tag them together at https://community.atlassian.com/t5/tag/new-ui-2018/tg-p might be a useful link for anyone who wants to have a look at those discussions
-
Indeed, that's a good conversation about the new issue view, rather than the Cloud layout changes.
-
It's not quite that. Boards do not "exist within a project" They are separate entities (although the more recent changes make a strong UI link between a project and a board). You can have many boards that draw issues from one or many projects. Boards are also not a filter. They use a standard filter (based on the issue…
-
Unless they've customised something to tell you, you can't really. I'd look at the project header and ask the project lead or admins there, they should know who the admins are.
-
Yes.
-
Ok, that's 1 and 2. You can't go back to 1 once you've upgraded.
-
You also have to paste the licence key into the licence box in the application.
-
No, it does not work. You can not use one database with more than one Jira Server application. You will find the second one shuts itself down when it spots the first is already running. Even if you manage to prevent that, you will immediately start corrupting the database, ruining your data completely. The docs for…
-
No. Each installation needs to be licenced separately. You need one licence for A and another one for B.
-
I don't know your organisations, I'm just an end-user of Atlassian software. You would need to ask one of your admins to grant you admin access.
-
Get your admins to copy the scheme, and apply the copy to your project(s) instead of the default one. You can then get them to amend that one without affecting the others.
-
No. Each installation needs to be licenced separately.
-
It looks to me like the system cannot connect to itself. Go find the "base url" (it's under "general settings" in admin), and, on the server, try going to that URL in a browser. Does that get you the login screen?
-
There's a dropdown at the top right of all the docs for versions of server and next to it a switch for "Cloud"
-
Only if you have "premier support". See https://www.atlassian.com/enterprise/support-services If you don't then you need to raise specific problems via https://support.atlassian.com/contact Or ask here in the community, we can try to help.
-
We are end users, we have no access to your Confluence or your spaces. Could you look at the log files to see what Confluence is doing when they try to attach files? Also describe the problem in detail - do they get errors? Warnings? Does the file go through an upload spinner?
-
Start with the two named jirasoftware<x>
-
You need to find the errors that were thrown when you tried to do the installation, and share the basics of the errors if you want help with them. But the errors should be telling you what went wrong directly.
-
Check the automatic assignee rules in the "components" section of the project, that is probably setting things.