32
Customers have installed this add-on in at least 32 active instances.
    by Broken BuildAtlassian Verified
    Broken Build is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

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

    Ask a question

    JIRA Service Desk
    This add-on is compatible with JIRA Service Desk.
    Supported
    Broken Build supports this add-on.

    Get support

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

    Custom project and issue type priorities with configurable sort order and default priority instead of global JIRA priorities

    Custom project and issue type priorities with configurable sort order and default priority instead of global JIRA priorities

    Flexible custom priorities configuration

    Apply priority scheme to multiple projects faster

    JIRA Service Desk ready

    Define custom priorities, custom sort order and default priority as priority scheme using configuration wizard. Map priority scheme to issue types in Issue type priority scheme to get priorities per issue type

    Apply priorities configuration to multiple projects at once when creating a new priority scheme or editing existing one.Default scheme if defined is applied automatically to all projects without schemes.

    Custom priorities work not only in JIRA Core and Software projects, but in Service Desk Customer portal too.Let your customers report an issue priority the way they want.

    More details

    Project Priorities add-on enables different priority sets per project.

    You can create Priority Scheme with required priorities and link it to a project so that user would select priorities in 'Priority' issue field from predefined values only. It also works for JIRA Service Desk customers in customer portal.

    For example you can have three projects where priority options can be configured the following way:

    Project A

    • Top
    • Medium
    • Low

    Project B

    • Blocker
    • Major
    • Minor

    Project C

    • Priority 1
    • Priority 2
    • Priority 3

    Even more - you can configure custom priorities per issue type using Issue Type Priority scheme as a mapping of Priority Scheme to one or more issue types.

    Project Priorities and Issue Type Resolutions add-ons solve JRA-3821 feature request.

    Contact us via support@brokenbuild.net or service desk if you need help or have any questions.

    User reviews

    (3)
    Sign in to write a review
    by Will Weaver on 2016-12-27
    This is a pretty straight forward, simple, and useful plugin. The main feature I'd like that would make this much nicer is the ability to choose the default priority for each scheme (or project if that's feasible).
    Was this review helpful?YesNo
    by Fabio Genovese on 2016-07-13
    I think this Addon is good to have differents classes of priorities for several projects. Useful. I'll write a review in my Italian Blog :-)
    Was this review helpful?YesNo

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons 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 add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on 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 tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications 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 add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Note: While this add-on has features specific to JIRA Service Desk, the add-on 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 add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

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

    Can I extend my free trial?

    For server add-ons, you can extend your add-on 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 add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons 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 add-on pricing is no longer available. You have two options for add-on purchasing:

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

    Learn more

    Broken Build is an vendor, committed to providing support for their add-ons at least 8 hours a day, 5 days a week.

    Vendor support resources

    Documentation

    Find out how this add-on works.

    Atlassian Community

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

    Versions

    Version 2.1.1 JIRA Server 6.4 - 7.3.6 Released 2017-05-23

    Summary

    Bug fixes and improvements

    Details

    In this release we have fixed a bug in priority replace during inline editing of priority field.

    When creating issues inline on agile board or issue navigator a priority will be taken from priorities configuration for that project and issue type.

    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 Project Priorities for JIRA via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Project Priorities for JIRA. You're prompted to log into MyAtlassian. Project Priorities for JIRA 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 Project Priorities for JIRA versions compatible with your instance, you can look through our version history page.

    Similar add-ons