Priority security setting didn't work for 1.4.23_62

  • garychuang
Posted: Mon, 05/12/2014 - 12:19

For example, a field is given a rule stating:
- For user A --> allow all
- For Status X --> Deny all

which should imply, when a issue is at status X, only user A can edit that field, others cannot view.

But when I upgraded the JFS to the 1.4.23_62, the above rule gave a result that NO ONE can view the field at status X.

Have tested in several environments, which gave the same results.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

The rule works perfectly with

  • garychuang
  • 04/04/14
  • Wed, 05/14/2014 - 08:52

The rule works perfectly with this snapshot.
Thanks a lot for the prompt response.

Just another issue I found.
When I create a freshly installation of JIRA and install JFS on it, all the servlet-related plugins seems to break down, and is running again once I disabled JFS.

To simply quote, all "http(s)://(hostname)/plugins/servlet/***" are not working

I turned to my older JIRA installations, and found out that when you use the "Update History Entries" function and after you updated all the fields, the above problem will occur.

Hi! Please try this snapshot

  • admin
  • 02/16/10
  • Wed, 05/14/2014 - 07:54

Hi!

Please try this snapshot build: http://dev.quisapps.com/artifactory/public/com/quisapps/jira/jfs/1.4.24_...

Do not forget to restart your JIRA after upgrading the JFS plugin.

Alex

After several testings, it

  • garychuang
  • 04/04/14
  • Mon, 05/12/2014 - 13:59

After several testings, it seems that the rule "current assignee" is not working.