Recommended C# Api for JIRA

[Zenit Kovacevic]

We would like to access the REST service through an existing C# API.

What we need is following:

• perform JQL querries
• create and update issues
• get a list of all available users (as multiProjectSearch in REST)
• get a list of all the available projects, issue types, transitions (for specific tickets), status
• available options for custom multiselect fields

Currently the Atlassian.SDK seems to be the most mature one, however it's poorly documented and doesn't support some of the above mentioned requirements. If we use it we might have to access the REST service anyway manually to perform the needed requests so it partially defeats the purpose of using such a library in the first place.

Are there any better options that we are somehow missing?

Thank you in advance,

Zenit Kovacevic

[Volodymyr Krupach · Accepted solution]

I would not bother about any libraries for JIRA REST. Just create you own own classes/methods that wraps JIRA REST calls you need. I am sure C# has nice libraries/classes for making http calls and serializing/deserializing JSONs.

It should not be too hard.

Other option is to contribute missing methods to the library you refer (if it's open sourced).

[Nic Brough -Adaptavist-]

Exactly. There are no "C# API"s because there's no need for them - REST is language independent - you poke JIRA with something and it responds with data (either xml or JSON). Whether you poke it with something written in Java, C, bash, perl, piaget, scala, Ook, etc, it's irrelevant.

[Zenit Kovacevic]

Thank you for your answers!

Atlassian.SDK were very responsive in implementing some stuff but we already ended up with making our own mini-implementation.

@Nic Brough [Adaptavist] There are "C# API's", just as there is a Java API to access the REST Service and they do make a lot of sense as long as you don't have any special requests outside of their scope that is otherwise provided by REST. Working directly with objects is significantly easier than having to write all the deserialisation/serialisation code yourself, especially when you're bound by time constraints (always). 

[Nic Brough -Adaptavist-]

They're not API's, they are libraries for interpreting the REST API. They're external to JIRA and rely on the raw REST API to be used. It's worth making the distinction.