by TWT Business Solutions GmbHfor JIRA Cloud, JIRA Server 5.0 - 7.0.11 and more versions
    Versions available for JIRA Server 3.5 - 4.4.5
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    Efficient search in your daily business

    Efficient search in your daily business

    Relatime indexing

    Security

    Easy installation

    Realtime indexing: The Connector guarantees a real time filling of the Google Search Appliance index.

    Consideration of the authorization scheme: In this way the GSA can identify during search queries which documents the searching user is allowed to see.

    Easy installation and Maintainance. Using the Google Search Appliance administrative interface and the adaptor dashboard there is always a indepth view of the indexing process and system status.

    Relatime indexing

    Security

    Easy installation

    Realtime indexing: The Connector guarantees a real time filling of the Google Search Appliance index.

    Consideration of the authorization scheme: In this way the GSA can identify during search queries which documents the searching user is allowed to see.

    Easy installation and Maintainance. Using the Google Search Appliance administrative interface and the adaptor dashboard there is always a indepth view of the indexing process and system status.

    More details

    FEATURES

    • Consideration of complex authorization structures that may be different depending on workflow status and therefore visible for different users.
    • You can accurately define via JQL statements which tickets you would like to index, e.g. “open and closed tickets not older than 3 months” or “tickets released as public solution”
    • With the new Google Plexi Connector Framework the connector is already future-proof
    • Intelligent caching system for the optimization of inquiries in the JIRA system especially for large environments
    • Because of the transmission of the ACL information during the indexing a connection to any authentication procedure (e.g. Kerberos, NTLM, SAML, LDAP/AD, etc.) possible
    • Supports also Jira OnDemand and supports usage of the SOAP (or REST) API (connector can now be operated in a pure REST, pure SOAP or mixed mode)

    More details

    FEATURES

    • Consideration of complex authorization structures that may be different depending on workflow status and therefore visible for different users.
    • You can accurately define via JQL statements which tickets you would like to index, e.g. “open and closed tickets not older than 3 months” or “tickets released as public solution”
    • With the new Google Plexi Connector Framework the connector is already future-proof
    • Intelligent caching system for the optimization of inquiries in the JIRA system especially for large environments
    • Because of the transmission of the ACL information during the indexing a connection to any authentication procedure (e.g. Kerberos, NTLM, SAML, LDAP/AD, etc.) possible
    • Supports also Jira OnDemand and supports usage of the SOAP (or REST) API (connector can now be operated in a pure REST, pure SOAP or mixed mode)

    User reviews

    (0)Sign in to write a review »

    There are no reviews yet. Be the first to review this add-on.

    Pricing

    This add-on is sold by a third-party vendor.

    Let us know that you'd like to manage this add-on's billing on your Atlassian invoice.

    This add-on is sold by a third-party vendor.

    Contact the vendor to evaluate or purchase this add-on.

    Paid-via-vendor pricing FAQ

    What does 'paid-via-vendor' mean?

    Paid-via-vendor add-ons are licensed and purchased directly through the vendor who makes this add-on.

    Payment for paid-via-vendor add-ons is not handled by Atlassian.

    Will paid-via-vendor transactions be on my Atlassian invoice?

    Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor add-ons will not be on your Atlassian invoice.

    Paid-via-vendor pricing FAQ

    What does 'paid-via-vendor' mean?

    Paid-via-vendor add-ons are licensed and purchased directly through the vendor who makes this add-on.

    Payment for paid-via-vendor add-ons is not handled by Atlassian.

    Will paid-via-vendor transactions be on my Atlassian invoice?

    Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor add-ons will not be on your Atlassian invoice.

    Support

    Google Search Appliance Connector - JIRA isn't formally supported.

    Google Search Appliance Connector - JIRA isn't formally supported.

    Versions

    JIRA Cloud Released 2015-11-16

    Summary

    Gerneal improvements and extended support for SOAP and REST API

    Details

    • A REST plugin for Jira is now available, which replaces the previous SOAP plugin
    • Improvements of the Windows installer
    • Added a config option to disable the usage of the SOAP (or REST) API (connector can now be operated in a pure REST, pure SOAP or mixed mode)

    Versions

    Version 2.1 JIRA Server 5.0 - 7.0.11 Released 2015-11-16

    Summary

    Gerneal improvements and extended support for SOAP and REST API

    Details

    • A REST plugin for Jira is now available, which replaces the previous SOAP plugin
    • Improvements of the Windows installer
    • Added a config option to disable the usage of the SOAP (or REST) API (connector can now be operated in a pure REST, pure SOAP or mixed mode)

    Installation

    Similar add-ons