Comments
-
Go to admin -> manage applications and you'll be able to add it in there.
-
If you've found the download button and got a local file, go to the "manage addons" and click "upload add-on"
-
You asked a broken question - you implied something couldn't be done on Cloud without explaining what it was you were trying to do. So I was confirming what you'd said. The recently updated macro is available on cloud, so it'll work. So I'm not sure why you're asking.
-
You can't use it, so you're stuck.
-
I'd use K15t's Backbone synchronisation to duplicate the project(s). Or iDalko's Exalate. I said Backbone first because it's the one I've worked with more recently (and I know it can do "sync over email" if you struggle with firewalls) You could build your own version with a bit of effort, but I think it's easier to not…
-
I'm afraid Cloud does not (yet) allow for external authentication, only internal and google accounts.
-
It's pretty much what the error message says - you've given Bitbucket connection settings which point it to a non-existant or firewalled database server. Check the hostname can be resolved from the Bitbucket server, and that you can reach it ("telnet folsom:5432" might be worth a shot on the server, as you'll get an error…
-
It is what the error message says - it can't connect to your database for some reason. Have a look around the error in the log - there should be more about it.
-
What mail server have you connected it to for sending email and where is that server? Is your account on that server valid?
-
Yes, there's no difference between an evaluation and a full installation system. An evaluation system simply stops allowing most functions at the end of the evaluation period.
-
This is mostly a duplicate of https://answers.atlassian.com/questions/28328/jira-and-sub-tasks - there's more information there. To answer this question though - no, you can't change this, it's not a flag, it's a deliberate design and Jira is doing what it's supposed to do. It's a nonsense to put in sub-tasks for…
-
You can use field configuration to hide some of them, but not many. The ones you find you can't hide are structural.
-
Um, actually, no. You need a licence that WAS valid at the time the version you are moving to was released.
-
That's not an Atlassian question.
-
Bhushans guide is a good one and he beat me to a link that helps - give him the "right answer" karma
-
I'm not sure what "generate a report by clicking on the newly added tab like all the other tabs" really means, but I'm guessing that what you mean is that you have got some code that creates a tab and does nothing else. If that's right, then then answer is simple - you need to do some more coding to generate the reports…
-
This appears to have nothing to do with Atlassian products. You should explain what it has to do with Confluence, or try asking elsewhere, in a forum that is more relevant
-
That's to tell JIRA that the directory you are using has nested groups. You'll need it turned on or your all-of-them group will appear to be empty!
-
My understanding of LDAP filters is pretty basic too, but yes, you can do things in JIRA with filters. I've only ever used simple ones like "only import users and groups from an OU=xyz", but that should do the job for you.
-
It'll be presented to JIRA as a group like the others.
-
JIRA doesn't do nested groups - you'll need to manually add all the users from each group into your internal group. It does read them and flatten them though, so if you created a nested LDAP group, you'd be ok (In LDAP, have a group called all-of-them, which just contains ABC, DEF and GHI. JIRA will see a group called…
-
You need to create an issue of a type which has a different workflow that does NOT have this post-function on it. Or, you could add a new custom field to the issue type (read only, no need to put it on screen), set it on the primary new issue, and then interrogate it and break oout of the clone process if it is found on…
-
No, I'm afraid you're still missing the point. I can't explain it again in any other way.
-
I'm not sure you're understanding the points made before, but it's clear we have differing opinions. Mine is that you're wrong because duplicate page names breaks search and fast use of the system for the main reason I use it. You think I'm wrong because you want the (in my opinion broken) search behaviour.
-
I can't get a definitive answer in one search. Therefore it's broken. The search, as it is already does multiple items. But I can't go straight to a definitive answer when you've got duplicate names.
-
I think we're going to have to agree to disagree. I've already answered that point several times. It breaks search, it's no good saying it doesn't. We disagree, and whilst I understand your point, I can't see how it doesn't break it.
-
Unfortunately, that's not quite right - duplicates always break search because you can't get a definitive answer in one go. Sticking a random number on the end is just making the page non-unique by botching it and making it ugly for the user. Consider a simple case - 400 software products, each with a space dedicated to…
-
No, it's the other way around in real life. Duplicated names break searching for the users, and this actually provides a far better experience for the users. What you're asking for, in your analogy, is for everyone in the car to have a steering wheel.
-
Again. No. The requests have been closed as "won't fix" in Atlassian's tracker.It's not an issue, they've done this by design. There's nothing to "fix" because it's not broken.
-
No, the requests have been closed as "won't fix" in Atlassian's tracker.