38
Customers have installed this app in at least 38 active instances.
    by OBSSAtlassian Verified
    OBSS is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for app quality, reliability, and support.

    Learn more

    for Jira Server 6.0 - 7.5.1
    Unsupported
    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Supported
    OBSS supports this app.

    Get support

    Data Center
    This app is compatible with the clustering and high-availability capabilities of our products.
    Jira Service Desk
    This app is compatible with Jira Service Desk.

    Custom fields that lets the user select issue(s) from a predefined JQL query

    Custom fields that lets the user select issue(s) from a predefined JQL query

    Custom fields to select issue(s) from a JQL query

    Multiple Field Types

    Dynamic JQL with Custom Display Patterns

    "JQL Issue Selector" plug-in allows you to create custom fields that runs a JQL query and lets the user pick issue(s) from the results of that JQL query.

    You can create fields from a collection of different field types including list selector, dropdown selector and label selector types. Single and multi selectors are supported for each.

    Dynamic JQL queries can be created using field values from the issue. You can create JQL queries that returns different results for the issue it's running on. You can also configure how options are displayed in the list.

    More details

    JQL Issue Selector allows you to run a predefined JQL query and use the results as the options of a custom field. This gives you the ability to represent any business entity as a Jira issue and use it on other Jira issues.

    A predefined JQL query means more control: Instead of linking Jira issues, you present applicable options to the user as a custom field (and even make it a required field).

    Multiple field types are supported: You can define a list field, a dropdown field or a label select field. Each with support for single or multi select.

    The differentiating feature of JIS is the "Dynamic JQL" feature which lets you take parameters of your JQL from other field values on your issue. This means the field can behave different for each issue. You can create dynamic fields like:

    • Subtasks of this issue.
    • Tasks assigned to assignee of current issue
    • Bugs in the same project or some specific project
    • Issues updated after this issue is created

    The View and Value patterns are also customizable.

    Reviews for cloud

    (3)
    Sign in to write a review
    by Chander on 2016-08-11
    I was wondering if you are planning on Related Field concept here and also for JQL Issue Dropdown Selector (Single Select), can we expect issue linking, right now it just shows as text rather it would be great if we have like a hyperlink feature to related issues
    Was this review helpful?YesNo
    by PJ on 2016-05-25
    Thanks for the reply. I believe if you are providing a non-free plugin, it should provide more features that a similar free plugin. After months of test, it seems that Query Issues Custom Fields plugin does all you offer plus 1) it's searchable 2) you can define default values. The question is: why should users pay for this plugin, if they can have another one for free with more functionalities?
    Was this review helpful?YesNo
    OBSS

    Hello PJ,

    You are right, default values are not supported yet but it is definitely in our short term roadmap. JIS 1.3 was a major renovation and we will continue to improve the plugin.

    JIS does support searching by display value but please be advised; since this is a text search you have to use exact words or wildcards, just like other text fields. Better search options is also in our short term roadmap.

    Finally, we are well aware of similar plugins in the marketplace and we admire them. They proved themselves to be useful also for us many times in the past. The main differentiator for JIS is the ability to define dynamic queries. That means you can define placeholders in your JQL and fill them with field values on the issue. This gives you the ability to change the available dropdown options for each individual issue. You can define a field that lists bugs assigned to the assignee of the current issue or you can define a field that selects from issues created before the current issue. The same field, works different for different issues. We believe this to be very powerful.

    Thank you again for your interest in our plugin. We will be happy to receive all kinds of feedback and real-life use cases. Please do not hesitate to contact us from plugin@obss.com.tr

    EmreT

    Reviews for server

    (3)
    Sign in to write a review
    by Chander on 2016-08-11
    I was wondering if you are planning on Related Field concept here and also for JQL Issue Dropdown Selector (Single Select), can we expect issue linking, right now it just shows as text rather it would be great if we have like a hyperlink feature to related issues
    Was this review helpful?YesNo
    by PJ on 2016-05-25
    Thanks for the reply. I believe if you are providing a non-free plugin, it should provide more features that a similar free plugin. After months of test, it seems that Query Issues Custom Fields plugin does all you offer plus 1) it's searchable 2) you can define default values. The question is: why should users pay for this plugin, if they can have another one for free with more functionalities?
    Was this review helpful?YesNo
    OBSS

    Hello PJ,

    You are right, default values are not supported yet but it is definitely in our short term roadmap. JIS 1.3 was a major renovation and we will continue to improve the plugin.

    JIS does support searching by display value but please be advised; since this is a text search you have to use exact words or wildcards, just like other text fields. Better search options is also in our short term roadmap.

    Finally, we are well aware of similar plugins in the marketplace and we admire them. They proved themselves to be useful also for us many times in the past. The main differentiator for JIS is the ability to define dynamic queries. That means you can define placeholders in your JQL and fill them with field values on the issue. This gives you the ability to change the available dropdown options for each individual issue. You can define a field that lists bugs assigned to the assignee of the current issue or you can define a field that selects from issues created before the current issue. The same field, works different for different issues. We believe this to be very powerful.

    Thank you again for your interest in our plugin. We will be happy to receive all kinds of feedback and real-life use cases. Please do not hesitate to contact us from plugin@obss.com.tr

    EmreT

    Pricing

    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.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

    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

    OBSS is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.

    Vendor support resources

    Documentation

    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.

    Versions

    Version 1.3.3 Jira Server 6.0 - 7.5.1 Released 2017-04-28

    Summary

    Bugfix release

    Details

    Bug

    Installation

    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 JQL Issue Select 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 JQL Issue Select. You're prompted to log into MyAtlassian. JQL Issue Select 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 JQL Issue Select versions compatible with your instance, you can look through our version history page.

    Similar apps