Comments
-
It's got direct access to the full API, it doesn't use REST for that.
-
What have you got in setenv.sh (same directory as start-confluence.sh) for the -Xmx parameter? Can you also try cat /proc/memstat on the box, and give us the first three lines? (Or MemTotal at least)
-
There are several reasons that can happen, you'll need to look at the configuration of the handler, and the log file to find out why it is happening here.
-
You have to ask the user. As I said already, Jira does not store the passwords. Where are you trying to "directly access the issues"? Is it a system which shares authentication with Jira? Could you enable SSO?
-
No. Jira does not store user passwords, so there is nothing to "get" here. What are you trying to achieve? Should the users not be using the "forgot password" when they forget them?
-
You can ask Atlassian to change it for your system (They will do it as a one-off, so pick your number carefully)
-
Yes, you will need an add-on. There are some that do little more than "create issue when a post-function runs" - you can add those post-functions to the "create" process (be careful not to loop them though!) There are others which give you a lot of flexibility on top of that. ScriptRunner, Power Scripts and Automation are…
-
Also, go to Admin -> Project roles and go over the "default members" for each role. Jira's default is to stick the "can log in" group into "Users", which leaves you in a right mess very quickly (unless you really do want an open-to-all automatically Jira). I'd condsider leaving "jira administrators" in the role of project…
-
a) In both cases, you need to be an admin to set up scripts, but users get to use the functions the scripts add (both of them support controlling which users can use the functions as well) b) Probably ScriptRunner. With Power Scripts, you have to learn a new scripting language. This is slightly easier than learning…
-
I accidentally installed a postgres 10 Jira last week (didn't check the version of postgres on Debian before starting on the Jira). It was ok at first, install and getting-started stuff all worked. It fell over in a heap as soon as I tried to use an add-on. Re-did the setup with a supported postgres and the same process…
-
Jira does not have fields with those +'s next to them by default. That suggests they are provided by an add-on. We don't know what they are, so Yogesh asked for the "type" of custom field as it would help us identify the add-on. Without knowing that, I am afraid we are a bit stuck. We can tell you it can be done, as…
-
Development is not covered by the courses. It is mentioned, but none of the courses are going to show you any code or builds. Specifically, to answer your questions * No. * Not for the courses. Although a basic understanding of XML and Tomcat would be a help if doing the Atlassian systems administration course. * There's a…
-
True. But the principle is still right. Run it on Linux. There should be a bit of a bias - if you have little or no Linux expertise in-house, then absolutely use Windows, as your internal support for it will be better. But if you have a free choice, or some Unix-like experience, use Linux.
-
You can customise applications to do SSO, but if you wish to use the SSO that Crowd provides, you will need to make the application use Crowd. Ann's last link in her answer covers that.
-
Where are you seeing "all the tasks linked to"?
-
All the default handlers will attach email attachments by default (some allow you to disable that)
-
It looks to me like someone has made a translation In English, the placeholder is simply "write a comment...", and I suspect the other languages say something similar to that when they are off-the-shelf. The length and some of the words in your picture make me think you have a modified language pack. A quick test - have a…
-
A quick note on your last point - Atlassian have a data centre in Ireland now, you could ask to be moved to that.
-
You cannot have Jira users without email addresses. I would consider adding an "integration" user with an email address that points to a mailing list or shared admin mailbox.
-
No, but I'm only a light user of Cloud, so I'm less likely to see it. When you say it "cannot create", what is the problem? Does it return you to where you were before with no message? Hang while creating? Or is there an error message?
-
I don't mean them to be derogatory. I am trying to understand what you are trying to report on, but I am frustrated by you not answering the questions I've asked in a meaningful way. My instinct is that you are not actually sure on what you are trying to report on either, which makes it impossible to form a decent answer.
-
Ah, sorry, I misunderstood. This needs to go to Atlassian Cloud support, over at https://support.atlassian.com/contact as we need to read the logs
-
Time to invest in a better mail server, I'd say.
-
I understand that, but you still need to define what you are trying to measure. "Status options for a release" doesn't really explain anything about what you're trying to do, let alone how you're seeing "progress" on it.
-
Use quick filters. One for assignee, one for stories and then probably one for "issuetype in subTaskTypes()" Status is probably not worth including, as the status will mostly be shown already by the columns in the board.
-
That error is about your Jira not being able to connect to the database. You should have a look in the application log ( <jira home>/logs/atlassian-jira.log ) as it should give you more of the error than the error you've got in the question, including the root cause of the failure.
-
The [] are a string representation of the fact you've got an list of somethings back from the field, not a string. Version pickers can hold many options, so your getCustomFieldValue is getting a list (often it'll be a list of one item), then just using "toString" outputs a converted value. You should not convert it, but…
-
I am sorry, but that does not make sense. Filters don't have a hierarchy because the items you've listed have no direct relationships. I suspect all you want is "Assignee in (list of users) and issue type in (list of issue types) and status in (list of status)"
-
It's the driver - in order to support later versions, the database driver has to be a higher version, one that does not support 7.9.2 (That was the case several versions ago, I suspect it's the same reason now)
-
Start at https://confluence.atlassian.com/enterprise/high-availability-guide-for-jira-288657149.html