techtalk / jirarestclient Goto Github PK

Currently, the NuGet package does not have a strong name and therefore cannot be used easily in projects that require strong named assemblies.

Suggestion: build the NuGet package with a strong named Assembly.

Attachments in fields at create of an issue not saved.

Hi,

Great tool by the way, the only issue I've found is that the Base64 encoding/basic auth doesn't work when you use email addresses as the login, against ondemand instances.

ie - username: [email protected] doesn't work, but username:import does. password same in both.

I suspect the encoding doesn't like the punctuation and special symbols, but I can't be sure.

passing "new string[2] {"status", "fixVersion" }" to EnumerateIssuesByQuery does not help. And I can't find any documentation for library. Thanks for help!

Hi,

is reading custom fields a supported feature?
If not, are there any plans for it?

Best regards

I previously used Atlassian.Sdk, but it is based on soap and that is going to be removed in a few weeks. Checking out this library, and I was wondering if it would be a good idea to support project versions?

Hi!

When I read Issues from jira using GetIssues(), EnumerateIssues(), GetIssuesByQuery(),
it receives timetracking fields OriginalEstimate, OriginalEstimateDays, OriginalEstimateSeconds null or 0.
Version is 2.5.0

With regards,
Peep Palts

JIRA documentation claims that JIRA supports OAuth for API authentication and I have personally confirmed that NTLM also works. Unfortunately, it doesn't seem possible to use anything other than Basic authentication with JiraRestClient.

If I submit a pull request to permit alternate methods of authentication, is there a good chance it will get accepted? I was thinking to add an alternate constructor to JiraClient that accepts a parameter of type IAuthenticator (defined in the RestSharp library) in lieu of username and password.

I was also thinking that it would make sense to use HttpBasicAuthenticator in the default case, rather than manually adding the Basic auth header to the request.

Standard issue fields should include "priority"

RestSharp 105 changed the BaseUrl property from string to Uri which breaks JiraClient.

CreateIssue(String projectKey, String issueType, String summary) has a type parameter, but the same is not available for UpdateIssue. Request to make a method to update the Issue Type as well.

Is there a way to get custom fields? It seems like the properties exposed in TIssueFields are basically what you get when interacting with an Issue.fields object. Are there any plans to incorporate custom fields? Maybe allow users to hardcode them? I cloned a copy of master and hard coded my own project's custom fields for a Netsuite integration, but this option is less than ideal when users could simply push an array of custom fields to populate.

We use the API to update a custom field when code is committed against an issue, or a build is done containing code for that issue.
We do this by instantiating an empty issue, adding the id and filling in the required field then calling UpdateIssue.

This works well and only updates the required field and leaves most of them unchanged, except the Labels and time tracking fields.

Looking at the source it appears that the check is for whether these are null rather than their initialised values (which appear to be an empty array and an Timetracking object).

It would be great if JiraRestClient could also provide a methode to add worklog to an isssue.

Currently only have the download URL from attachment.content, one have to use another webclient and authenticate again to download.

creating jira bug with TechTalk.JiraRestClient : {"errorMessages":[],"errors":{"timetracking":"Field 'timetracking' cannot be set. It is not on the appropriate screen, or unknown."}}

Hello @techtalk
There are a lot of issues and PR's that haven't been responded to.
Are you still actively maintaining this project?

I need to integrate with jira and currently deciding between this client and https://github.com/peoplesbeer/AnotherJiraRestClient

cheers

I updated a previously working application to JIRA REST Client 2.3.0.1 / RestSharp 105.1.0 and now CreateAttachment fails - Popup says "JIRA Integration Error" - Creation of the JIRA issue failed: Method not found: "RestSharp.IRestRequestRestSharp.RestRequest.AddFile(System.String, System.Action1<System.IO.Stream>, System.String)".

I changed the reference to the .NET 4.0 RestSharp, as suggested in restsharp/RestSharp#690 as a work around, but still no joy.

Using the .NET 4.0 client version on the Jira Rest Client side.

Anyone else seen this problem?

Code:
foreach (FileInfo issueAttachment in IssueAttachments)
{
using (FileStream ss = new FileStream(issueAttachment.FullName, FileMode.Open,
FileAccess.Read, FileShare.ReadWrite))
{
client.CreateAttachment(issue, ss, issueAttachment.Name);
}
}