Comments
-
Are you on Cloud or Server? Have you adjusted anything in the admin "look and feel"?
-
I think you need to explain what you mean by "doesn't work", because it works perfectly in the places I've seen it implemented.
-
Use the OS to look at the size, and then delete it.
-
Actually, point 1 is correct. If you take something into a sprint, you are saying you are committing to doing all the effort required to complete that piece of work. If you reject it during the sprint, you have done all the work needed to complete it, so the reporting is correct. What I suspect is wrong is your estimation…
-
I really want to go to Moscow.
-
I do not understand what you expect an "upload of a directory" to do. Confluence only holds files as attachments, but you say "not attachment", so I would like to ask you to explain what you want the upload to do?
-
I am guessing you are on Cloud Confluence, where you have explicitly signed up to take the "latest version" at all times?
-
I am just trying to help you work out what your system is doing and why it is behaving that way. Given the facts you've given us, you removed the issues from the sprint, so they won't show in the sprint any more.
-
So, when you try "sprint = X", do your closed issues appear? If they do, then we may have a bug. If they do not, then you have removed them from the sprint, so they will not appear on the board. It doesn't matter what rules you think you've set, you've removed them from the sprint.
-
Pff, Summit is ok usually, but this time we have Community Day, which is going to be the best bit.
-
The xml will not have the production licence in it, but once it is all running, you can just paste it in.
-
Usually under <confluence home>/export
-
What does the log file say the problem is? (On the server, <confluence home>/logs/atlassian-confluence.log is the place to start, but check the other files in that directory if that has no errors)
-
"unable to see" suggest that you're not using a scrum board, or that you have not created any epics or versions yet. There is no "reset". You are free to delete all your projects and configs for testing if you want, but for a completely clean Jira cloud, you will need to provision a new one.
-
We're not support here, we are a community of end-users. Even if we were, Atlassian does not do that sort of work. I would strongly recommend you engage one of their solution partners for this. Visit https://www.atlassian.com/partners/search?page=1 for help with selecting some to talk to. Also, as I work for one of them,…
-
My guess is that you have not set the "base url" to where your Jira really lives. Go to Admin -> General configuration and change the base url to jira.mycompany.com
-
For which? Guessing you are asking about 6.2, that ended in (late) 2017 if memory serves. Not that it matters when it ended, as all you need to know is that it is ended.
-
You have copied and pasted this script from somewhere without reading it properly. It's html encoded and you need to convert it back into the original plain-text
-
Indeed, the earliest Jira still supported is 7.3 at the time of writing this (that goes to January 2019), so 6.2.7 is way way past its end of life.
-
They do. There are newer drivers in later versions of the software. They do not back-port drivers (or other things) into older versions of the software, as that would require large amounts of testing and possibly development. If you want to use newer drivers, upgrade.
-
Each one of those errors has a "find out more" link. Try reading what they have to say. Then come back here if the explanations don't help. (In most cases, you will find they will, but "most" is not "all")
-
I'm going to dodge the "console" question because I don't really have one. I was lucky enough to have a computer around long before consoles made an impact in gaming and also tend to play games that computers are as good as, or better than, consoles do it. As an example of that, I'm not a good gamer. I do play first person…
-
You're right. It might happen, but I totally agree that almost nobody selects a Cloud application on the basis that "we cannot break it" We do select Cloud applications because they do what we want and someone else has to deal with it breaking. This approach directly leads into those of us who have to deal with a system…
-
Looking at the driver is a good idea, it makes sense. But the Jira you have was written to support the specific version that is distributed with it. Changing the version might fix some things (unlikely, but possible), but that would only fix appserver-to-database issues. It won't affect Jira-to-appserver issues, and could…
-
You need to run a proxy web server to do that. A proxy can present many <server>/service:port combinations as though it is a single site. I tend to use Apache to do it with "proxypass/proxypassreverse" pairs, but other web servers can do it just as well (or better!). Nginx, Lighttpd, IIS and so-on. A snippet of my Apache…
-
It was the right version to use at the time 6.4 was built. If you want the software to work, and be supported by Atlassian, you need to use the versions of the database, hardware and drivers that they state they support. If you replace the JDBC driver, erm, well, don't. There is no good reason to do so, and the only…
-
Yes. They will support it. When it has passed all the testing on both sides (database and application)
-
Very good idea. I especially like the split into pre/post, so that you would have a script that an admin runs to put themselves in a place where they can edit, then a second to do all the work of applying it. There is a difficulty in the second script, in that Jira does loads of checks on "activate" and may start asking…
-
Correct. Although the user may be notified by other references in the notification scheme.
-
Edit the page, and look for the areas where the attachments appear. You should see links to them, or possibly macros that call them. You should be able to delete these bits and the attachments will no longer appear after you save and go back to view. If that process is not working, could you explain at what point it fails,…