128
Customers have installed this add-on in at least 128 active instances.
    by CoreSoft Labsfor JIRA Server 7.0.0 - 7.2.2 and more versions
    Versions available for JIRA Server 6.2.1 - 6.4.14
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    CoreSoft Labs supports this add-on.

    Get support

    Fine-grain security for custom fields. Restrict view or edit permissions on a per-field basis

    Fine-grain security for custom fields. Restrict view or edit permissions on a per-field basis

    A set of Security-enabled custom field types

    Simple and powerful permission management

    All data access methods secured

    New custom field types. Almost every JIRA native custom field has its secure equivalent. We deliver such types as: text (short and long), number, date/time, user picter, group picker, list (single and multiple choice)

    JIRA Administrator can define secure field permission schemes. It looks similar to JIRA Permission schemes. Separate permissions can be defined for view custom field, edit and view field history.

    All data access methods are secured. Unprivileged user can't access field neither within JIRA nor via API or exports.

    More details

    Completely new approach to JIRA security. This plugin brings field-level security to JIRA. Now you can easily manage access to each custom field separately for view, edit and view history permissions.

    Almost all JIRA native custom field types have their secure equivalents including:

    • Secure Data Picker
    • Secure Date Time Picker
    • Secure Free Text (multi line)
    • Secure Short Text (single line)
    • Secure Select List
    • Secure Multi Select List
    • Secure Number
    • Secure User Picker
    • Secure Multi User Picker
    • Secure Group Picker
    • Secure Multi Group Picker

    Unlike other solutions this add-on covers all data access methods including exports, velocity templates and API calls.

    An extra JQL search function can be used to search for secure fields values in issue navigator.

    User reviews

    (3)
    Sign in to write a review »
    by Oleksii Dziapko on 2016-09-15
    Dear developers, I try to use your plugin, but after one or two changes (link field to the different scheme) I came across with a problem: now my custom filed (in column Related) linked to Default Secure Fields Configuration Scheme and also to my custom Secure Fields Configuration Scheme and I can't, in case if I want, delete this custom scheme, because if I click to the name of field in column Related (where I can select Permission Scheme for Custom Field) to the related custom filed scheme it says that scheme has already chosen as default. Here is the printscreen: http://prntscr.com/ci8i3u
    Was this review helpful?YesNo

    CoreSoft Labs

    Thanks for your review!

    We're working on eliminating bugs and adding new features continuously. We're serious about software quality so if you have any other questions or want to report a bug, we encourage you to contact us through our support portal.

    CoreSoft Labs Team

    by Anthony Arnett on 2016-03-31
    Works like a charm. Vendor support is really helpful and responsive. Thanks guys!
    Was this review helpful?YesNo
    by Tiep Pham on 2016-01-20
    This add-on can not show in filter. How can i show this filed in the filter. Thanks
    Was this review helpful?YesNo

    CoreSoft Labs

    Thanks for your review!When developing this add-on we focused on strong security features, so if you want to search against secure fields you shall use JQL Functions we designed. Please find out our documentation to get some more information. Standard JQL search is not possible due to JIRA architecture limitations.If you have any other questions, we encourage you to contact us through our support portal

    CoreSoft Labs Team

    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.

    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

    Support

    CoreSoft Labs supports Secure Fields for JIRA. You can visit the support site to get help.

    Get support

    Versions

    Version 1.1-jira7 JIRA Server 7.0.0 - 7.2.2 Released 2016-04-07

    Summary

    Bug-fixes and migration performance improvements (for JIRA 7.x)

    Details

    This release includes:

    • minor bug-fixes
    • custom fields migration process improvements
    • inline edit improvements

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

    Similar add-ons