Prevent outside vendors from accessing next-gen project with limited permissions

[Adam LaMore]

Hello,

We use Jira for our internal projects as well as to coordinate with some outside vendors. By default, we used groups and permissions to so that new "classic" projects are accessible to all internal users (jira-software-users group), and groups of outside vendors (each vendor with their own group) would be added to specific projects as necessary.

With next-gen projects this is broken. We only have "open," "limited," and "private" as permission options for next-gen projects. Both "open" and "limited" allow viewing for all users, with no way that I can find to block specific users/groups. So the only option remaining is private, which means that every specific user has to be invited. As far as I can tell there's no way with next-gen projects to allow our pre-existing permission scheme.

Right now I've had to disable next-gen projects entirely as individual users are creating them and not locking down the permissions appropriately to block outside people.

Any suggestions?

[Tarun Sapra · Accepted solution]

Here is your answer - https://answers.atlassian.com/questions/156863

Make sure you have assignee field on the edit screen of the issue.

[Tarun Sapra]

has you issue been resolved?

[Tarun Sapra]

See here - http://stackoverflow.com/questions/19671317/400-bad-request-http-error-code-meaning

Make sure your JSON is per the API specs

[Tarun Sapra]

From the docs - "The simple way to update an issue is to do a GET, update the values inside "fields", and then PUT back."

Thus do a get request and then then a put request with the same json data and just modify the "assignee" filed to a proper user ID , "me" isn't a userId it seems which you are doing right now.