Field not consistently read-only with inline editing
*This issue has moved*
This issue has been moved permanently to Adaptavist's Product Support JIRA instance.
All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the
Can't access your account link in order to reset to a new password.
I've got a custom field and I've created a behaviour that should make that field read-only ... except that it doesn't. I can still edit the field. I've tried turning on logging for Behaviours but I cannot find any logging output for the plugin.
Here are the settings I've used:
Use Validator Plugin: Disabled
Guide Workflow: None
Field: Organisation, Optional, Readonly, Shown, Conditions: None.
Mapping: Developer Technical Support (the project), all issue types
Here is the XML:
<config use-validator-plugin="false" name="Read-only organisation" description="Used to make the Organisation field read-only" guideWorkflow="null">
<field id="customfield_10601" required="null" readonly="true" hidden="null"/>
This is affecting the inline editing capability in JIRA, in that hovering the mouse over the custom field causes the editing UI to be displayed. HOWEVER, if I then click on the Edit button then cancel, the inline editing is correctly disabled. Refreshing the page causes inline editing to work again
JIRA 6.3.9 with Service Desk 2.2 and Script Runner 3.0.7.
Happens also on JIRA 6.4.12 with the latest version. It is seemingly random. Sometimes fields will become disabled after a significant delay. Sometimes if I refresh they are disabled right away. Other times they just won't be disabled.
Just to add, though, we have other scripts running on issues as well (custom developed ones).
Also the configuration is
When: user in jira-users
Except: user is joe.bloggs
user is fred.smith
MySQL 5.6, JIRA 6.4.4, Chrome. Sometimes people can use inline edit, then they open the Edit screen in a new tab, where they cannot edit the field, they close the tab and reload the issue view screen, and sometimes that disables the inline editing of the field as intended.
I'll try to get some more time to test, but it looks like on our test instances, inline editing is consistently disabled, as expected.
With a similar setup, our production instance is not (experience described in my earlier comment). Some differences between the two are:
Production instance is secure (https), test instances are not (http).
Production instance has a load balancer, test instances do not.
Production instance is using an Oracle db, test instances are on MySQL.
Do any of these match up with the rest of you? I doubt the database matters, but could running behind a load balancer and/or running over https be the reason why it's not working as expected?
I got this with JIRA 6.4.4 and SR 3.0.16. Any ideas on how to gather useful information to help debug the problem?