Basically the jira-administartor has all the rights in the permission scheme.But still , though we update via a soap call , its not been changed and says we dont have enough permission to edit the issue.This occurs in very few issues.The issues in the same project and same issuetype are changed for some issues and not for some issues.May I know the reason why this happens? and is there is a way to change directly in the data base.
First, no, avoid editing the database - it's a last resort because you need to stop Jira, get a proven backup, run the SQL, restart it, reindex and then test it very carefully. You can destroy a Jira by hacking it's database.
If the issues that aren't changing are in the same project and there's a pattern in the issue type (e.g. they're all bugs failing, while improvements and features are fine), then you can be almost certain that there's a permissions or configuration tied to that causing the problem.
You've spoken about permissions already, but the important thing here is that SOAP respects the permissions. Log in as the user that SOAP is using and see if you get the right to change assignee in the UI. I suspect you'll find you don't, and the usual cause of that is permissions.
However, permissions are project level and you've said only some issue types, so I suspect SOAP is not giving you quite the full story. I would also check the EDIT screen to make sure that the assignee field is on the screen - if it's not, SOAP may be dropping it too. On top of that, check the field-configuration for the project - if the assignee is hidden in there, SOAP will be unable to set it, same as the interactive user...
Also, bear in mind that permissions can be dynamic - you can do things like "only reporter can assign the issue". SOAP respects all of those.
Depends on the permissions the reporter has to assign (or be assigned?) the issue.
Ok, so assignee is on screen in the Edit screen, but does it appear for the user that you are running the SOAP stuff as? Do they get the "assign to" link too? Is it definitely an update and not a transition? Have you checked the field configurations for that issue type?
I don't think there's any point in fixing the data in the database here - the fact is your config is blocking this somewhere, and you need to fix that in the long term.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot