Implement Administration API's

[maartenba]

See the following URL's for documentation:

• https://www.jetbrains.com/help/youtrack/standalone/Project.html
• https://www.jetbrains.com/help/youtrack/standalone/Groups.html
• https://www.jetbrains.com/help/youtrack/standalone/Role.html
• https://www.jetbrains.com/help/youtrack/standalone/Permissions.html
• https://www.jetbrains.com/help/youtrack/standalone/Issue-Link-Types.html
• https://www.jetbrains.com/help/youtrack/standalone/Custom-Fields-RestAPI.html
• https://www.jetbrains.com/help/youtrack/standalone/Statistics.html
• https://www.jetbrains.com/help/youtrack/standalone/YouTrack-Setup-Methods.html

Perhaps good to split the work for this in separate issues and PR's.

[aschoelzhorn]

I'm implementing the API for
https://www.jetbrains.com/help/youtrack/standalone/Project-Custom-Fields.html

[maartenba]

Sweet! Thanks @aschoelzhorn

[maartenba]

Thanks, logged #70 for that.

[nylchr]

I'm tempted to start with https://www.jetbrains.com/help/youtrack/standalone/Project.html but it raises the question about class definitions. There's already a Project class, derived from https://www.jetbrains.com/help/youtrack/standalone/Get-Accessible-Projects.html, with a vastly different definition than the two different versions that https://www.jetbrains.com/help/youtrack/standalone/Project.html offers. There's also a Project class in the Agile Boards namespace with the same signature as one of the new ones. I propose an inheritance hierarchy with Project (containing only the id) as base.

Actually, it would be even better if all API calls returning a project returned the definition found at https://www.jetbrains.com/help/youtrack/standalone/GET-Project.html
{ "name": "Test Project", "id": "TP", "description": null, "archived": false, "lead": "login.name", "startingNumber": null }

Any suggestions on how to proceed?

[maartenba]

There can be a new Project class in the new (to be created) namespace for this? I'd say best to stick close to the API's, so having a specialized Project for each scenario seems feasible. Okay with inheritance regarding having a project id across all.