Having: a team with id=13 and an a person with id=104
I've tried:
curl -uuser:password -X POST -H 'Content-Type: application/json' -d '{ "resources": [ { "person": { "id": "104" } } ], "availability": [ ] }' http://jira/rest/teams-api/1.0/team/13
obtaining: no output message whatsoever and the person was not added to the team either
Input validation
Both
return the expected entities
Sthephen,
We're not using context (the /jira/ part). That the URL entry is good is verified by the fact that http://jira/rest/teams-api/1.0/team?ids=13 does actually return data
This is what I'm trying to add a person to a team
curl -uuser:password -X POST -H 'Content-Type: application/json' -d '{ "resources": [ { "person": { "id": "104" } } ], "availability": [ ] }' http://jira/rest/teams-api/1.0/team/13
Hello again Javier,
I tested on Jira 7.12.3 with Portfolio and confirmed the following;
We did run into an issue when attempting to add a person as a resource and a person to a team. As you confirmed, you do not get a response (which is the default response currently in the API) but a user is not created.
We are looking further into this to see where the issue is and if it is possibly a defect in the product. Please allow us some time to investigate further.
Regards,
Stephen Sifers
Hello again Javier,
There is a method you can use to create a resource within Portfolio. When creating the resource it will be created as a virtual user. You can run this method for example:
curl -u user:pass -X POST -H 'Content-Type: application/json' -d '{ "teamId": 1, "person": { "title": "admin","jiraUser": {"jiraUserId":"admin"} }}' http://jira.server.name/rest/teams-api/latest/resource
We did confirm this will create a resource within your team.
Regards,
Stephen Sifers
Thanks Stephen!
Person is an entity in portofio. Then we have jira users, which are not the same
person, should/shouldn't/either pre-exist in porfolio?