Conversation
fc2e8a3 to
7d91995
Compare
|
Fixed PR to deal with Travis checks errors on but does properly return them for: so I needed to replace the I suspect this is an issue with the Travis check itself as I cannot reproduce it with my Jira installation, and the API clearly states that watchers should be retrievable either by issue ID or Key (see https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/issue-getIssueWatchers : |
Fixes sumoheavy#291 Declares `path` for API GET calls using not `issue.self` (which produces full URIs) but `client.options[:rest_base_path]` Resulting API calls will not have repeated URIs which are raising `request_client.rb:16:in `request': JIRA::HTTPError` Works For Me (TM)
7d91995 to
e6ea639
Compare
|
Force-pushed commit to amend author email due to local git misconfiguration |
|
@kali-hernandez could you add a test for this? |
|
Why you do this only on certain ressources? And not on all? @kali-hernandez |
|
Tests fail for ruby 3.0.6, 3.1.4, and 3.2.2. [1] JIRA::OauthClient authenticating with oauth the access token initializes[2] JIRA::OauthClient authenticating with oauth the access token initializes[3] JIRA::Resource::Filter returns issues |
Fixes #291
Declares
pathfor API GET calls using notissue.self(which produces full URIs) butclient.options[:rest_base_path]Resulting API calls will not have repeated URIs which are raising
request_client.rb:16:in `request': JIRA::HTTPErrorWorks For Me (TM)