Missing a docstring.

Should be localized.

Mind elaborating here on when it's rendered?

You can simplify this a bit by starting off with:

if not value:
    return ''


Lines will be less crowded that way.

Can we maybe use templates for rendering instead of hard-coding HTML here?

This isn't true for this function.

Swap these.

Should be localized.

This is in the wrong import group.

Missing a period.

We should catch exceptions and log them so this doesn't crash if something goes wrong (network issues, data issues, whatever).

This view should use CheckLoginRequiredViewMixin and CheckLocalSiteAccessViewMixin.

Can you do:

.asana-field {
    &.selectize-control.loading:before {
        ...
    }

    &.selectize-dropdown {
        ...
    }
}

Too many colons.
Can we use a class instead? I have a change pending for post-3.0 that will get rid of FontAwesome spinners (which are broken and officially deprecated in terms of being recommended) and replace them with a non-wobbly spinner. It will require a <span> of some sort, and it'll be easier for me to update this if we're not duplicating FontAwesome CSS here.

IDs before classes.
Same with others further down.

Instead of hard-coding 13px, can we use an existing variable definition?

Can we defein variables for the colors being used? Here and below.

What do we need flex here for? It still doesn't have wide-enough working support.

This can nest in #field_rbintegrations_asana above.

Same comments here about double colons and using a span.

No need for parens here.

Looks like we're duplicating the one from the Python field. Can we standardize these somehow?

Better as callback.bind(this).

If you do:

if (apiKey.length === 0) {
    return;
}


You can save an indentation level and reduce the line widths for the rest of these.

You can simplify to:

$accessToken.on('change keyup', changeWorkspaceEnabled);

Alphabetical order (case-insensitive for dependencies).

Can we set a logger = ... above, and use that here and anywhere else we might be logging?

The mixins must go first.

I just mentioned this in the Trello change as well, but the one thing I want a better assurance of is that data from Local Sites can't leak, and that this will be safe on RBCommons.
Can you add unit tests for anything involving Local Site/configuration/review request accesses?

Ship It!