@epriestley this is already a vast improvement, thanx for D15093: Migrate existing projects to retain "Workboard" as default item.

Yes gray is terrible for accessibility and gray on gray should be avoided at all cost (and for some reason designers love this :) ). (Dark gray on (near) white however, can very much increase readability enjoyment compared to black on white)

It's an accessibility issue:
http://webaim.org/resources/contrastchecker/

Foreground color: #2980b9
Background color: #daeaf3
Contrast Ratio: 3.49:1

No longer required because of D11036

Small note: on OS X output like this is often translated if you configure your machine to run in a different language.

@epriestley, we have some code in MW, that parses the xml of the svg, to extract it's viewbox, which you can consider to be a 'original size' and use in the calculations for your target size.

Yes, with his LDAP credentials.

Interesting now it says: ./bin/remove destroy rTEST
I updated the repo, perhaps it got fixed already ? Or did i choose a different 'entry' path into the dialog or something.... will look further.

This is mostly because the autocomplete starts resolving from the root of the repo, instead of from the 'import only' subpath. If you manually add the subpath it seems to work.

Seeing the same problem with my install...

So in terms of migration, would it not be possible to split the auth provider in two (JIRA5 and JIRA6) and just let users re-couple their accounts in case of a JIRA5 to JIRA6 upgrade ? We use LDAP auth as primary auth methodology anyways.

Proposed an initial doc update here: https://secure.phabricator.com/D9307

/me like the new layout.
I was just going to file a ticket on this, and I see it's already done !

Also posted the problem description with 1Password. http://discussions.agilebits.com/discussion/25233/continuous-request-to-save-password-on-configuration-form?new=1

This actually makes it difficult for me to migrate away from JIRA :(