Accessing the Jira REST API of a On-Demand Jira instance


I am currently trying to create a migration tool to moove Issues from one Jira Instance to one hosted on Atlassians On Demand platform. Unfortunately the jira-rest-java-client (version 0.6-m3) is allways giving me a code 301 (Moved Permanently). The Url I am using is "" ... reading from the old repository works fine.

Is there anything special with the On-Demand Jiras? Does the URL have to be different? Is the Jira installation that new, that my rest client is too old for it? If yes, where do I get a version that works?


1 answer

1 accepted

2 votes
Answer accepted

Aaaahh ... I hate when that happens ... the problem was simply that I had to use httpS instead of http ... sorry for having botherd you guys :-(

fyi... JIRA Command Line Interface 2.6.0 has a bunch of enhancements that were added to support my migration to an OnDemand instance. I will be posting more information on the migration in the next few days - for now see Migration from Plugin Studio

Just dropping a note in saying thanks for coming back to note the https problem. I was having the same issue, and made the same mistake. Your answer saved me some pain, and some velocity on my facepalm.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Thursday in Jira

Updates to give you visibility into what's coming in Jira Server and Data Center

Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...

324 views 1 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you