Service Account User Not Seeing Issues in Sprint

[Ralph Callaway]

I just migrated some automation over to using a service account user. I've got the scopes dialed in, but it's not getting any results for the getIssuesForSprint endpoint. The same request returns lots of results when run from the browser.

If I open my browser and paste this relative URL `https://MYCLOUDDOMAIN.atlassian.net/rest/agile/1.0/sprint/MYSPRINT/issue`, i'm getting something like this

{
  "expand": "schema,names",
  "startAt": 0,
  "maxResults": 50,
  "total": 79,
  "issues": [
...

When I make the same call as the service account user to the api endpoint `https://api.atlassian.com/ex/jira/MYCLOUDID/rest/agile/1.0/sprint/MYSPRINT/issue` I don't get anything

{"startAt":0,"maxResults":50,"total":0,"issues":[]}

The service account user is able to get sprints just fine via the `/rest/agile/1.0/sprint/123` endpoint

I'm assuming this is a project permission issue. But when I go to the appropriate groups and click 'Add User' there is no ability to add the service account user.

Is there a secondary mechanism I need to be using to get the service account access to sprint issues?

[Ralph Callaway · Accepted solution]

Instead of groups, go to the permission scheme directly. You can update permissions, e.g. Browse Projects', and when you select individual user the service accounts show up.

[Trudy Claspill]

@Ralph Callaway 

Did you confirm that was actually possible?

In my testing I could add a Service Account to the project in a role, but could not add it as an individual User in a Permission scheme. I tried both the friendly name of the Service Account and the auto-generated "email" address of the account.

[Trudy Claspill]

Hello @Ralph Callaway 

Is this a Service Account that was created through the Admin hub (https://admin.atlassian.com) under Directory / Service Accounts?

Have you added the service account user to a Role in the Spaces for issues are contained in the specified Sprint?

[Ralph Callaway]

yes, the service account was created through directory/service accounts

i can see them as an option to 'Add People' to individual spaces. but we have 100s of spaces, and every time a future space is created we'll need people to remember to add the service account, which isn't feasible

i need some mechanism to get them into a group that can be associated with the permission scheme for all projects

[Trudy Claspill]

Do please let us know if you are able to add the service account to the Permission Scheme. I was not able to do so in my own instance with either the name or auto-generated email of the service account.

If it doesn't work a go-forward solution is to add the service account user as a default member of 1..n global Project Roles. They will then be added to each new project created. However, that works only for Company Managed projects. For the pre-existing project you would have to implement a solution using the API to bulk add the service account to roles in the existing projects.