Comments
-
It's actually highly efficient, in the one single area that matters for an index file: speed. Shared file systems are simply too slow to serve up index files at the rate even a lightly used JIRA system needs it to.
-
https://docs.atlassian.com/jira/REST/cloud/#api/2/issuetype-createIssueType says nothing about "Issue Type:" - that's not the right structure for it.
-
There is no bulk-clone in JIRA, so you'll need to either do a single clone, 52 times, or use one of the add-ons that provides "bulk clone"
-
I am stuck then - it suggests the browser is sending something which triggers a process which fails, but if the application logs say there are no errors, it can't have started it, or you would see errors in there.
-
You can raise it with Atlassian support if you've got a commercial licence (25+ users), and try with evaluation, but they will refer you here or to their documentation. You've not said what you've looked at, so here's my list of things to check * The confluence user doesn't own and have full access to the file system under…
-
A sub-status doesn't really do much for you, it's just a field. You could base a swimlane on the custom field instead, but you'd lose the in-progress swimlane. Or you could meld them and have two swimlanes (jql would be status = x and field = y, and status = x and field != y)
-
I'm guessing you're installing on a server without a windowing server installed. That's not a problem, it's just an interface layer and not needed. What are the errors you get when you try the installer with the -c so it doesn't try to fire up X?
-
No, they're bundled into a language pack - look in <jira install>/webapp/WEB-INF/atlassian-bundled-plugins/ for .jar files with language names/ids in their name.
-
No, that should be fine, Confluence will be using a bundled Java, which is good. There should be further errors in the log following this - more "caused by" lines. As you've ruled out the java and a couple of other problems, it's well worth looking urther down there.
-
Before you restart, change this one back: "I Changed class.resource.loader.cache from true to false" It's fine in a development system that's going to get restarted soon, but without the cache enabled, the templates gradually chew up space in memory and will lead to performance problems eventually.
-
That does not make sense. A status is the current status of an issue. An issue will only have one status at a time.
-
Could you explain what this has to do with Atlassian stuff?
-
Atlassian have stated that all their UX research indicates that "none" is the best way to handle this. So it's not going to change, because it's simply not a problem for the vast majority. I agree with Steven - just because we think you're doing the wrong thing, you've asked, you've seen why we think it's wrong, and it's…
-
Usually something structural with the ownership of files, broken database connection, wrong version of Java. Have a look at the log file - what does that say when you hit "next" after pasting a licence in?
-
Bother, I was hoping you might be on a version where that worked. The two other options are 1. Throw it away - use the "reset defaults" option at the top of the list and start again 2. Deal with your fielditis - more than two or three status type fields means something is wrong with your design.
-
No, you need to amend the language files on the server, or create a translation file and upload it as an add-on.
-
Ok, that means that your python can't be logging in correctly, as it's not able to "see" the create screen for that project. I've not used Python to do this sort of stuff, so I'm stuck. The code looks ok to me, but obviously the connection thing isn't being set correctly.
-
You don't use phpMyAdmin or downloaded "installed" drivers for JIRA to do any of this. By all means, use phpMyAdmin to *create* a MySQL database for JIRA to use, but that's where the involvement ends. Download JIRA and run the installer, it will tell you if it needs drivers (and where to get them and install them) and then…
-
My current instinct is to create a "translation" that gives it another name.
-
There are several possible causes * The confluence user doesn't own and have full access to the file system under the installation and home directories * A virus scanner is blocking access to files * You are running it as "root". * A an application blocker is stopping it - SELinux for example * You've set a JAVA_HOME and…
-
The response you are getting tells you what the problem is - you are giving it a load of field data for fields that are not there in your system You should check what fields you do get by using the UI to create a similar issue.
-
Ok, if they're not on the list, and they can't be mentioned then they don't have the "can use confluence" rights.
-
There's too little information here to give you much. What is ALM (there's loads of tools out there with that in their name), what are you trying to import, and how do you want to do it? Push or pull?
-
You can only "edit" the issue type if the configuration of the source issue type is the same as the target issue type. The configuration means essentially "fields and workflows". I think that explains your case - you can create issues fine, with the new type, but you can't just flip the issue type because the one you're…
-
There's no specific "archive", you'd simply download the ones you wanted to keep to dump on storage somewhere and then delete them from the issues.
-
Pretty much - you can't edit it to blank, as there's no option in the edit drop-down to do so.
-
Hmm. I'm not sure I understand that. Could you not set the security level automatically on create, and then place the security level on edit screens for them to edit later? That would reduce the problem to "we don't like the name 'security level'" which is completely understandable. But you could put explanatory test with…
-
I'm afraid your questions are irrelevant. You do NOT insert data into a JIRA database. You should do imports via the UI or REST. Never the database.
-
I'll go a step further and point out that I've removed those hacks before because people don't get that an empty line means "none". I've never had any problem with users not understanding "none".
-
Several, but none of them are particularly fun. * Bulk-edit, resolve and then re-open them again * ScriptRunner has a canned script for fixing them * Change the workflow so it has a transition from closed to closed and sets a resolution, use bulk-edit to push them through it.