136
Customers have installed this add-on in at least 136 active instances.
    by quisapps.comfor JIRA Server 6.3 - 7.2.2 and more versions
    Versions available for JIRA Server 4.0 - 5.0.7
    JIRA Server 5.1 - 5.1.8
    JIRA Server 5.2 - 6.2.7
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    quisapps.com supports this add-on.

    Get support

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

    Hide or make read-only custom fields, time tracking details, assignee field. Restrict access to JIRA Agile

    Hide or make read-only custom fields, time tracking details, assignee field. Restrict access to JIRA Agile

    Create a field security scheme

    Select from a number of available conditions

    Set access rules for JIRA Agile plugin

    Field security scheme defines a set of rules applied to chosen fields. Choose between full access, read-only mode or no access at all. Apply the scheme to one or more projects via project configuration.

    JFS offers a set of different conditions which can be applied to each rule.

    To complete a time tracking security add restrictions to JIRA Agile (formely GreenHopper) access

    More details

    • Set access permissions to custom fields, Assignee and Time Tracking
    • Manage access to JIRA Agile

    User reviews

    (21)
    Sign in to write a review »
    by Seshu on 2016-09-01
    Hi, On our test environment we installed the latest Field Security Pluging version (jfs-1.4.33_71.jar) and jfs-patch-1.3.0-7.1.9-patch.zip as per your instructions. However, after the upgrade, we are unable to start JIRA instance. Our JIRA instance is 6.3.1 (Hosted on Server). We get the following error in the log. Can you please help? I am unable to login to your Support website. 2016-08-31 18:42:34,565 localhost-startStop-1 FATAL [atlassian.jira.startup.ComponentContainerLauncher] An Error occurred during ComponentContainerLauncher servlet context initialisation - com/atlassian/jira/issue/history/ChangeLogUtils : Unsupported major.minor version 52.0 (unable to load class com.atlassian.jira.issue.history.ChangeLogUtils). java.lang.UnsupportedClassVersionError: com/atlassian/jira/issue/history/ChangeLogUtils : Unsupported major.minor version 52.0 (unable to load class com.atlassian.jira.issue.history.ChangeLogUtils) Hello, We are planning to upgrade to JIRA 7.2.0. Is the latest Field Security Plugin version compatible with JIRA 7.2.0? If not, can you please provide an ETA when it will be supported? Thanks Narayanan Seshadri
    Was this review helpful?YesNo

    quisapps.com

    This is a support request - please mail to support[at]quisapps.com or raise an issue at http://support.quisapps.com. Thanks! Alex

    by Patrice Foerster on 2016-01-29
    This is add-on is very good. We are using it to hide time tracking details and related custom fields from external users.
    Was this review helpful?YesNo
    by Tiep Pham on 2016-01-21
    Can this plugin show the secure fileds in the filter function?
    Was this review helpful?YesNo
    by Snezana Lazarevska on 2015-01-05
    __
    0 out of 2 found this review helpful
    Was this review helpful?YesNo
    by Simon Kegel //SEIBERT/MEDIA on 2014-12-10
    You can set view/write permission for each field in a project and depending on a status - that's really great :-) A little improvement would be a dependency on the issuetype just like the status conditioning. That's why I gave just 3/4 stars.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    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.

    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

    quisapps.com supports Field Security Plugin for JIRA. You can visit the support site to get help.

    Get support

    Versions

    Version 1.4.34 JIRA Server 6.3 - 7.2.2 Released 2016-09-19

    Summary

    Compatibility with JIRA 7.2 and bugfixes

    Details

    • Compatibility with JIRA 7.2
    • Fix for broken symbols when system encoding is not UTF-8 (no extra settings required)
    • JFSSUP-209: return unmodified response for REST search query when there are no issues in response
    • JFSSUP-210: removed excess logging when processing invalid issue edit request
    • JFSSUP-213: compatibility fix with Traffic Light plugin
    • Fix for "Assertions$NullArgumentException: query should not be null!"
    • Other stability fixes

    Installation

    Similar add-ons