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?
There is a way. Create a transistion with the following
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs