Field Security Plugin for Jira

by quisapps.comfor Jira Server 8.1.0 and more versions

Versions available for Jira Server 4.0 - 5.0.7.1
Jira Server 5.1 - 8.0.2

Unsupported

Jira Service Desk

Supported

Jira Service Desk

Unsupported

Jira Service Desk

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

Reviews for cloud

(28)Sign in to write a review

by Victoria Lozano Rodríguez on 2017-07-04

This plugin has a very useful functionality, but causes the error: Error rendering 'com.atlassian.jira.plugin.system.issuetabpanels: changehistory-tabpanel'. Please contact your JIRA administrators. The error is documented in confluence: Https://confluence.atlassian.com/jirakb/jira-issue-activity-tab-shows-errors-376832019.html Please fix the bug. My version of Jira is 6.4

0 out of 1 found this review helpful

Was this review helpful?Yes No

quisapps.com

JIRA restart will most probably fix this. Please also note that you must restart JIRA immediately every time you modify JFS state via UPM - this includes enabling, disabling, upgrading etc.

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?Yes No

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

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?Yes No

by Tiep Pham on 2016-01-21

Can this plugin show the secure fileds in the filter function?

1 out of 1 found this review helpful

Was this review helpful?Yes No

by Snezana Lazarevska on 2015-01-05

0 out of 3 found this review helpful

Was this review helpful?Yes No

Reviews for server

(28)Sign in to write a review

by Kubo Qubson Grznarik on 2018-12-13

Im using this plugin for several years now. Bugs I had were minor and were solved in updates of the plugin. Great work.

Was this review helpful?Yes No

by Vijaya KUMAR Koleti on 2018-11-28

Should've tried if it is a straight forward installation. I couldn't find rollback / uninstall it's patch if something happens.

1 out of 1 found this review helpful

Was this review helpful?Yes No

by Jacky Jin on 2018-03-10

A very good plug-in, we can config field permission now.

0 out of 3 found this review helpful

Was this review helpful?Yes No

by Cuenta Jira on 2018-02-22

This plugin crash Jira, dont install this, if you have problems with jira remove jar file of the installed plugins

6 out of 8 found this review helpful

Was this review helpful?Yes No

by Balvant Biradar on 2017-10-18

This plugin should be used very carefully because it needs modification in Jira installation directory Support for this plugin is really excellent and very quick turnaround is there. Appreciate your best support service and help

1 out of 1 found this review helpful

Was this review helpful?Yes No

Reviews for Data Center

(28)Sign in to write a review

by Victoria Lozano Rodríguez on 2017-07-04

0 out of 1 found this review helpful

Was this review helpful?Yes No

quisapps.com

JIRA restart will most probably fix this. Please also note that you must restart JIRA immediately every time you modify JFS state via UPM - this includes enabling, disabling, upgrading etc.

by Seshu on 2016-09-01

Was this review helpful?Yes No

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

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?Yes No

by Tiep Pham on 2016-01-21

Can this plugin show the secure fileds in the filter function?

1 out of 1 found this review helpful

Was this review helpful?Yes No

by Snezana Lazarevska on 2015-01-05

0 out of 3 found this review helpful

Was this review helpful?Yes No

Cloud Pricing

Server Pricing

Data Center Pricing

This app is sold by a third-party vendor.

Let us know that you'd like to manage this app's billing on your Atlassian invoice.

Pricing FAQ

What does 'paid-via-vendor' mean?

Paid-via-vendor apps are licensed and purchased directly through the vendor who makes this app.

Payment for paid-via-vendor apps 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 apps will not be on your Atlassian invoice.