Hacker News new | past | comments | ask | show | jobs | submit login

I can't speak for leftcoaster, but what drives me crazy about the upgrade process is this: http://confluence.atlassian.com/display/JIRA041/Upgrading+JI...

I'm just upgrading from 4.0 to 4.1, I shouldn't need to create a new installation, a whole new database, re-download, install, and configure every plugin I use, disable e-mail access, etc...

I want to be able to run an upgrade script, or drop in a new war and when it starts up it asks if I want to upgrade things. Or an inline upgrade. Look at Wordpress, Gallery, MS Office, any OS, etc... for examples.

My startup uses Crowd, Jira, and Confluence. However, due to the complexity and risk (we've had issues crop up in the past) of upgrading, we tend to run several versions behind, waiting until there's some "must have" new feature or improvement.

And while we do use Crowd (and while I generally really like Atlassian products) the Crowd LDAP support is really lacking, and the complexity of hooking Jira/Confluence into Crowd is a pain (no write support for Fedora 389?). It should be a simple flag, maybe even changable from the admin. Not a bunch of hacking in .properties, .xml, and libs.




Upgrade points noted.

JIRA 4.3 and Confluence 3.5 will make it much easier to connect to Crowd. No editing of files required.

We don't have write support for the Posix schema scheduled for Crowd, I'm afraid, so no promises on that front.


I think the only reason we're using Crowd now is to map LDAP groups into Jira.


We've had Crowd deployed for two years to handle web app auth. Configuration, deployment were a bit painful.

We're pulling it out and writing our own - seems to be the only way to get necessary features such as delegated administration which have been on the Crowd roadmap for years now.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: