Permission Scheme and Field Configurations preventing Soap from updating fields

[Sjoerd Peters]

Let me start by explaining the goal. I have a jira project where anybody can create an issue, after the issue is created the duedate, priority and fixversions will be set via Soap, based on the value of a custom field. The priority, duedate and fixversions fields should not be editable by any normal user but they should be able to see these fields.

The problem I'm having is that when you remove the priority or fixversions field from the edit screen of the projects 'screen scheme', you can't edit the field using the Soap API either.
If I include the fields in the edit screen but hide them using the 'fields configuration' page I get the same result.

The only field I found a solution for is duedate by only allowing the admin group of witch the Soap API user is a part of to 'Schedule Issues' using the projects permission scheme.

So is there a way to have multiple edit screens for different users? Or is there a way to set the values of an issue via Soap regardless of any 'screen scheme' settings?

[Renjith Pillai]

There is a way. Create a transistion with the following

• has the destination as the same status
• can be executed only by the user or group which is used in Soap
• associate a screen to this transistion with the fields that you want to update
• using Soap perform this transistion and supply the field values.