Jira Server 5.1 - 8.14.1
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
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
(32)Sign in to write a review
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.
This is a support request - please mail to support[at]quisapps.com or raise an issue at http://support.quisapps.com. Thanks! Alex
Reviews for server
(32)Sign in to write a review
Hello Maria Victoria,
JFS license model is in general just the same as the license model used by Atlassian for Jira Server. The license does not expire, but support & maintenance period expires. Support & Maintenance renewal policy is ruled by the clause 7 of the JFS EULA: Subsequent Renewal Periods commence upon the expiration of the prior Software Maintenance regardless of when it is purchased. This means that upon purchasing of, say, 1-year renewal, this 1 year will be added to the current expiration date of your support & maintenance period and not to the current calendar date. You may find the similar statement for Atlassian products here.
In this particular case support & maintenance period expired more than a year ago, so it is just cheaper to purchase a new license than to renew an existing one to reactivate its support & maintenance in order to use the most recent JFS versions, and that was my recommendation.
However I sincerely apologize for so delayed reply to your support request. I definitely should not have kept waiting for so long.
With best regards,
Alexander
Reviews for Data Center
(32)Sign in to write a reviewJIRA 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.
This is a support request - please mail to support[at]quisapps.com or raise an issue at http://support.quisapps.com. Thanks! Alex
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.
quisapps.com provides support for this app.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 1.4.66_815 • Jira Server 8.15.0 - 8.15.1 • Released 2021-02-12
Summary
Jira 8.15 compatibility
Details
Jira 8.15 compatibility
Installation
- Follow Installation Manual
Similar apps
