Not possible to update an existing issue? about jira-ruby HOT 7 CLOSED

For what it's worth, I also noticed that the request was leaving the '/' off of the beginning of the URL (e.g. 'https:jira.example.comrest/api/2/blablabla' notice the lack of '/' between 'com' and 'rest'), and what fixed this for me was removing the '/' at the end of the host name I gave the Client object.

I changed

client = JIRA::Client.new(
  username: username,
  password: password,
  site: 'https://jira.example.com/', # notice the '/' at the end
  context_path: '', 
  auth_type: :basic)

to

client = JIRA::Client.new(
  username: username,
  password: password,
  site: 'https://jira.example.com', # the '/' has been removed
  context_path: '', 
  auth_type: :basic)

from jira-ruby.

I should mention that I'm authenticating with HTTP Basic and that the API user has access to update the record, which I confirmed by logging in as that user and updating the record.

from jira-ruby.

@endymion I feel your pain. However, your disparaging comments are not productive. The maintainers of this gem volunteer their time to maintain a gem that someone else created, and are under no obligation to help you. I'm sure they don't appreciate your negative tone. If it's so bad, why don't you try using one of the 60 other JIRA gems.

I realize it's not mentioned in the README, but there are two files in the repo which list a lot of examples, including updating issues. Perhaps you did not see these examples?

• Examples using OAuth
• Examples using HTTP Basic

I agree, the readme needs some improvement. However, docs aren't a replacement for getting your hands dirty and reading through the source code.

from jira-ruby.

Good news, guys!
I have fixed it!

The issue was that sometimes url didn't have '/' prefix.

https://github.com/legkvla/jira-ruby/commits/master

legkvla@3508d06

from jira-ruby.

Have created pull request for you, so you can better understand what's happened and how it could be fixed: #112

from jira-ruby.

#119 fixes this issue.

from jira-ruby.

I found bug in my last fix I made last summer. Since issue is still open - I would like provide a pull request.
Also I found conditions when issue reproduced - for example, when you use Attlassian SDK and your jira instance installed not in root context but in /jira path instead.
If somebody experienced this issue - could you please test my PR too and confirm that it fixes issue. After it will be done - we can close the ticket.

from jira-ruby.