dotMenu overrides ScriptRunner Read-Only Behaviour for Fields

[Dev]

I'm not going to retype my message lost through this messaging interface with all the steps taken to reproduce the error. So please ask me if you need extra information.

Read only behaviour works for fields, unless the dotMenu is called and the field name is entered in the prompt. Then from the issue screen, the user can edit and save new information in the read-only field. 

Why is this happening? Assuming this is a limitation, which limitation does it fall under? Is it breaking or altering the Javascript on the issue page?

Thanks in advance for your time. 

[Nic Brough -Adaptavist-]

If you drop the information you had before, we are going to struggle to help, as we are missing information we probably need to see. 

If you have "lost things through this messaging interface", then it begs a question of what you are doing that loses the things you have lost.

Please explain what you mean by "dotmenu" and then explain what you see vs what you think you should get.

[Dev]

Steps:

• Add a read-only behaviour
• Make an exception for a specific user
• open the issue details screen at example.org/browse/key and try to edit
• Expected behaviour: beyond documented limitations field is read-only except when specific user. 

My issue that I'm inquiring about occurs when you follow the steps above, then: 

• press . on keyboard to display a prompt (viz., dotMenu)
• type in the read-only field name
• Expected behaviour: only specified user can edit and save changes.
• Actual behaviour: any user can now edit and save changes to the read-only field. 

Assuming this is a limitation, which limitation does it fall under? Is it breaking or altering the Javascript on the issue page?

[Dev]

If you have "lost things through this messaging interface", then it begs a question of what you are doing that loses the things you have lost.

I believe my session timed out as I spent too much time trying to detail my issue. I clicked submit and I lost all of my post and could not click the back button to retrieve it due to the UI interface. So going forward, I'll try to keep my questions concise and provide information when requested as demonstrated. Do you have an answer?