Customers have installed this app in at least 37 active instances.
    by acocon GmbH - business division greeniquefor JIRA Server 7.0.0 - 7.3.8 and more versions
    Versions available for JIRA Server 6.1.1 - 6.4.14
    acocon GmbH - business division greenique supports this app.

    Get support

    Gadget plugin that lists tickets of an OTRS System and allows for conversion to JIRA issues

    Gadget plugin that lists tickets of an OTRS System and allows for conversion to JIRA issues

    View all your OTRS queues on your dashboard

    Assign your ticket to a project

    The newly created JIRA task

    View all your OTRS queues which are relevant for you to work with on your JIRA dashboard without having imported anything into JIRA previously.

    When converting an OTRS ticket to a JIRA task you can assign it to any project or user, set a priority, select its type and add the relevant versions as well as a description.

    The new JIRA task provides you with all information you entered previously and with a direct link, ID and label so you can always track where this task came from. You can see all connected OTRS tickets as well.

    More details

    It is widely known: working with two separate systems can be very impracticable. That's why PrOps stands for Projects and Operations. It connects the service and support level of OTRS and the project management in JIRA with a direct interface. With the PrOps ticket manager you can view your OTRS tickets directly on your JIRA dashboard without having imported anything previously. Using this overview you can easily create JIRA issues with a predefined list of options including projects, issue types, versions, assignees and a field for the description.

    List of core features:

    • Gadget for viewing OTRS tickets on the JIRA dashboard regarding multiple queues, an user or an user group
    • Creating JIRA issues with a flexible connection between the two systems
    • Connecting multiple OTRS tickets with one JIRA issue and the other way around
    • Subject and description gets transferred automatically
    • Possible configuration of
      • Shown columns, labels and information
      • status indicators

    User reviews

    Sign in to write a review
    by Jan-Peter Rusch on 2015-01-05
    Cool! Works (nearly) as designed. By now, the OTRS-Ticketnumber is not mapped to a newly created JIRA custom field, whereas the OTRS Ticket ID is. A label marking all OTRS tickets converted to a JIRA issue is not displayed in JIRA. Waiting for a back sync to OTRS, when a status change in JIRA is made. Also, closing a ticket in OTRS should close the issue in JIRA & vice versa.
    Was this review helpful?YesNo
    acocon GmbH - business division greenique
    Thank you for your review! The issues you stated have been filed and forwarded. The OTRS / JIRA sync regarding status changes and closing tickets is still beeing worked on and will be part of a future release.


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing?

    Apps are billed based on the number of users in your host product. For JIRA Server 7.0 or later, the app tier should match the maximum tier of the licensed JIRA products on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of JIRA Server prior to 7.0, the app tier should match the licensed user tier for JIRA. Even if fewer users want to use the app than your JIRA license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.

    How can I buy apps for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

    • Purchase the app at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the app at the same tier.

    Learn more

    acocon GmbH - business division greenique provides support for this app.

    Vendor support resources


    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.


    Version 1.8.1 JIRA Server 7.0.0 - 7.3.8 Released 2017-06-21


    Minor Bugfixing


    • Fixed a bug regarding status filter at the backend configuration


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate PrOps for JIRA - Integrate OTRS via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for PrOps for JIRA - Integrate OTRS. You're prompted to log into MyAtlassian. PrOps for JIRA - Integrate OTRS begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older PrOps for JIRA - Integrate OTRS versions compatible with your instance, you can look through our version history page.

    Similar apps