Comments
-
If the disk filled up, it's quite likely your index became damaged, but probably not the data in the database. The error you're seeing there is likely to be happening very late in the startup process, and Jira is actually mostly starting, but it's difficult to tell from just that. Are there other errors happening before or…
-
The screenshots are too low-res to see properly. What happens when you try to edit the page? It looks like you've managed to create an untitled page (possibly by using invalid characters in the title), and the best fix would be to give it a title.
-
So, you have created a new page, set the space default to be the new one, so the old page is not really used? When you go to the old page now, and try to delete it, what, exactly, is the error message?
-
Ok. Can you try this: * Create a new page * Change the space's home page to that new page * Go to the old page and try to delete it
-
No, I'm afraid not. Are you trying to delete this page or not?
-
But you said you were deleting it. I don't understand what you are doing.
-
I suspect what's happening is your deletion of the home page lands you back on the home page, which it needs you to recreate because it needs it. Don't delete home pages and you should be ok.
-
But it doesn't. It works with any user who has the privilege to create a valid database. A lot of the corporate and government clients would simply not allow an external process the elevated rights required for setting up the database correctly, so there's no need for a "wizard".
-
I don't think you can do this directly. The JIRA REST API does expose issues and field data, but the subversion tab you are seeing is not technically issue/field data - it's a display of data scraped from somewhere else. You could cheat a bit - if you could write a "derived field" that displayed the same information that…
-
I'd raise this as an improvement with Atlassian, as there's nothing there that does it at the moment.
-
Quite probably. I'd expect permission errors mentioned by Giuliano to throw errors into the logs, but that's not always the case.With nothing going into the log at all, it's quite hard to find anything specific, so I'd go with "raise a support call with Atlassian" next!
-
what does the atlassian-confluence.log say? It should at least echo "an error occurred while uploading" in there.
-
The list of components available is defined per project. I suspect you've got a list of components defined for the first project, but none for the second (so, in the second, Jira has no list to present to you, hence nothing to edit) As a project administrator, go to the project header and edit the list
-
Oh heck, yes. I've not really run into it directly with Atlassian stuff, but from my career before I found Jira 2, yes, that gets very odd. Stuff you can happily export to one country with a simple label can't go to the country next door without 200 process checks. It's not even stuff you'd associate with risks - military…
-
I'd forgotten that point about data rights - the Cloud servers are located in the US, are subject to the Patriot Act and hence you need to think about the impact of that on your data. Most of the time, it's fine, but if you store any personal information on individuals, you're pretty much guaranteed to break European data…
-
The main "con" for moving from server to Cloud is the loss of flexibility on addons and limitation on some functions. For example, you can't use external user directories on Cloud (only the internal accounts or Google apps). The list of addons you can use is strictly limited to the ones Atlassian are willing to support.…
-
You just look at the issue view. Click the "issue history" tab for the full history of changes, and the "work log" tab for each individual line of time spent (the aggregated time is shown in the main section already)
-
Ah, excellent, you have tried it. If that has not fixed it, then I think you may have run into an issue.Could you try disabling, and re-enabling the plugin and check the log for any errors.After that, I'd raise it with Adaptavist (I don't work directly on our addons, but I'll poke the owner too, the team may well have seen…
-
Because you can't use it until the data has been upgraded.
-
The addon needs to perform upgrade work on your existing forums data - it has detected older data that it cannot work with. I'd suggest you backup your Conflluence and then click the "upgrade to version 2" link
-
Yes. (Or, if you miskeyed, then chilli? ketchup? HP?)
-
Yes, there are some.
-
TExt fields aren't offered because it's not going to be of any use. The problem with a text field is that there's nothing to make the users consistent and the field is not "countable". Even if you can get your users to enter exactly the same text every time (which is unlikely), there's nothing in Jira to count it. If you…
-
It may have a workflow property set to prevent editing in a status. The field must also be on the edit screen to enable inline-edit in the view screen. But. NEVER put the resolution on an edit screen. If you do that, then anyone who clicks "edit" will set the resolution, which will immediately break your JIRA if the issue…
-
Yes, there is an addon called that.
-
I think that sounds more like blueprints, but they won't necessarily cover all the things that go into a theme.
-
True, some themes (built in, and downloaded) can have some flexibility at a space level, they're not totally rigid. And, of course, if you write your own, you can build in that too.
-
There's three answers, although they are all based on the same principle: Confluence themes are implemented as add-ons. So, you can: * Download them from the marketplace * Write your own * Use one of the more powerful theme editors that look like they implement one theme, but allow you to build up your own inside them and…
-
Pretty much as I said before. Jira lets you raise issues in a project via email. If you want to import more than just a flat description, you need something more clever, i.e. JEMH (because it's easier than writing your own code)
-
As Timothy implies, this is not a clear question. My best guess is that you want to have emails that raise issues in a project and tag it with a relevant component? This isn't possible in the standard mail handlers. You could write your own (bear in mind, you will need to come up with some sort of rule about how Jira is to…