Comments
-
The boards do not have any way to do side-by-side columns.
-
I don't think you are asking the right question. I don't think it will tell you what you want to know when I answer the posted question. The answer is "yes, it is licenced"
-
Space tools -> Attachments
-
There's no point in me copying and pasting from that answer and the linked docs. I can't tell you more than they do.
-
It's a workflow property on the status. You can edit the workflow and remove it if you need.
-
As an attachment on the page
-
No, "hacking your own code" means what it says - you need to write your own code to change the layout, and insert it into the application.
-
Note that 7.2 is out of order in the selection box at the moment (this is because of a patch that was retro-fitted after later versions were release)
-
The only time you won't get a log file that tells you what is going wrong is if the installation is so damaged, it can't start, in which case, you will see errors when running the start-up script. There is a reason in your logs, you will need to find it (it will usually be at the end of atlassian-confluence.log or…
-
Yes, as Joe says, there's no point allowing someone access to one room in a building if you have not granted them any permission to get into the building at all.
-
The link you have named there explicitly tells you how to do this. Please, read it properly.
-
What do the logs say the problem is?
-
Ah, I missed that "n permission schemes there is no transition permission to a group". Yes, you can do it. Allow the group transition permission in the scheme, then block the people you don't want to use it with conditions.
-
Both options tell you the flags the JVM is running with, including any GC options. If none are set, then it is running with the defaults
-
You will need to talk to the add-on provider, as their server is not working.
-
Yes, this is what conditions are for. A condition stops users from using a transition unless certain criteria are met, usually user related ones like "user must be in role or group" or "user must have permission x" I don't understand what you mean by "I had put that condition for that specific transition but since in…
-
Inside Jira, look at the system information page. From a command line on the server, the output from ps -ef will give you the flags the JVM is running with.
-
See your previous question - https://community.atlassian.com/t5/Jira-questions/Jira-Improvement-Change-Java-GC-mode-switch-to-G1/qaq-p/794179
-
Jira does not have field level security, so there's not a lot you can do here. If you mean "hide field from users", you can't. Jira is a collaboration tool, and hidden data is an anathema to collaboration, so it doesn't do it. If you want to stop people editing a field, then you need to move the edit into the workflow.…
-
See https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html But, the short summary for these versions is "download the new version, run the installer and point it at the old version's installation". If you have customisations in the installation or Apps, you may need to think a bit more,…
-
Add a custom field for the "solution version" and then explain what you mean by "locking" to us, because it is not clear.
-
Take the exported file, import it into a temporary dev system on 7.8, upgrade that to the same version as the target system, then export again.
-
Use Jira as it was intended and do not estimate on sub-tasks
-
That very much depends on the add-on. The data for add-ons usually remains intact when you remove one, but often becomes invisible or unusable. For Gliffy, that works by attaching two files to a page, a gliffy coded file and an image to display that's built from the coded file. If you remove the add-on, both files remain…
-
Admin -> Custom html
-
JaC no longer accepts simple bug reports, they have to be filtered through support (because there were so many that weren't bugs and needed to be support calls instead) Go to https://support.atlassian.com/contact and follow the most appropriate route.
-
I thought it might be. Your licence entitles you to use any version released before the end date (and you can continue to use it after expiry, but you cannot upgrade). 5.8.1 was released after the end of your licence. The highest you can use is 5.8.0
-
What is the expiry date on the licence?
-
What version are you running, when does the licence expire and what is the exact error message you get?
-
The shared directory is for the nodes in a DC cluster to share, it's not supposed to have anything to run in it. You need to look in the installation directory.