Jira 5: Anyone already updating?

[Ath]

Hi,

Now that Jira 5 is coming in the near future, and we (the company I
work for) are planning to upgrade to that version, it's required for
Jira-Extended-Webservice to be updated to conform to the new Soap
internal interfaces, or it won't be usable any longer.
There have been quite some changes to that interface, but as I didn't
originally develop this extension, and I'm not that experienced in
Jira-related programming, I haven't taken a stab on it yet.
If someone already succeeded to update the extended-webservice, please
respond (by private mail if desired), to see how we can make this
either publicly available, or available to me/us on a paid basis.

As an alternative, I'm starting a PoC soon to investigate a switch to
the REST based services, that have been available since Jira 4.x, but
where too limited to be used as we required. Current REST interface is
quite mature though, so it sounds as a viable alternative. (for
my .NET 4 based Client/connector application).
If the PoC works out successfully I won't be using the SOAP interface
any longer, and I also won't be pushing this SOAP interface anymore,
as I see no use in 2 similar but technologically different interfaces,
with 1 being the ugly/underdeveloped/hardly supported step-child
called SOAP. This last reason was the original reason to be using this
extended-webservice in the first place :)

If this PoC doesn't succeed, I'll be trying to upgrade the current
extended-webservice to the new Jira-5 standards/requirements, but
that's Plan B.

Any response is highly appreciated!

Regards,
Ath

[Matt Doar]

I agree that the direction to take remote access to JIRA is REST. I work with a number of clients who have their own SOAP-based tools and I'm recommending that they add REST to them now, and then gradually change their methods to use  the REST methods to access JIRA. However there are still some methods in SOAP that are not present in REST yet, so both will be needed for a while.

~Matt

Ath

--
You received this message because you are subscribed to the Google Groups "jira-extended-webservice" group.
To post to this group, send email to jira-extende...@googlegroups.com.
To unsubscribe from this group, send email to jira-extended-webs...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jira-extended-webservice?hl=en.

[Mario Ivankovits]

Hi Ath!

I switched the company and am no longer using Jira at all ... for the moment at least. I am still in contact with my previous company, but I am not sure what the plans are about any upgrade to Jira 5.
As long as there is no bad need for it, I think they will not upgrade.

Though, even if this is the last thing you'll do, please share your findings with REST! :-)

Thanks!

Ciao,
Mario

> -----Ursprüngliche Nachricht-----
> Von: jira-extende...@googlegroups.com [mailto:jira-extended-
> webse...@googlegroups.com] Im Auftrag von Ath
> Gesendet: Donnerstag, 02. Februar 2012 21:31
> An: jira-extended-webservice
> Betreff: Jira 5: Anyone already updating?

> --
> You received this message because you are subscribed to the Google Groups
> "jira-extended-webservice" group.

> To post to this group, send email to jira-extended-
> webse...@googlegroups.com.

> To unsubscribe from this group, send email to jira-extended-

> webservice+...@googlegroups.com.

[Ath]

Matt, Mario,

It's great the both of you are still reading this group!

I'll start my REST adventures soon, and report back here with any
progress I make.

Thanks,
Ath

[Mayer, Jonathan]

Morning guys,

I've found this extension invaluable as you may remember. Looking forward to seeing what you come up with for Jira 5.

Be well,
Jon.

Matt, Mario,

Thanks,
Ath

To post to this group, send email to jira-extende...@googlegroups.com.
To unsubscribe from this group, send email to jira-extended-webs...@googlegroups.com.

[Ath]

Hi,

Received a response from the Atlassian Jira project JRA:
<quote>
     [ https://jira.atlassian.com/browse/JRA-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roy Krishna [Atlassian] updated JRA-7205:

-----------------------------------------

       Resolution: Answered

    Fix Version/s: 5.0

           Status: Resolved  (was: Open)

The JIRA team has made the conscious decision to stop investing in SOAP. All our efforts will be with REST. This feature request can be done in REST.
</quote>

This makes it clear that the only real option is REST now, and there is no future for this extension starting from Jira 5.0.

I'll be starting real soon on developing my replacement connector, but that won't generally replace the Extended Webservice, nor be available as open source!
My connector will be using REST exclusively, to avoid a double login and using mixed technologies. And because every programming environment has it's own way of interfacing with REST, any 'common' solution won't be feasible or even useful.

For those interested, please study the REST interface definitions available from Atlassian, linked from this blog-post

Regards,
Ath

[Mario Ivankovits]

Thanks for the info!

 

Hopefully the REST API is featurefull enough so that an „Extended REST“ lib won’t be necessery.

Since I am no longer using JIRA, I have no plans to invest some time into the Jira REST API.

 

I try to update the website anytime soon to show that this project has been replaced by the Jira REST API.

 

Even if our project was not that active it was fun to work with you (all) together. :-)

Thank you!

 

 

Ciao,

Mario

--

You received this message because you are subscribed to the Google Groups "jira-extended-webservice" group.

To view this discussion on the web visit https://groups.google.com/d/msg/jira-extended-webservice/-/KVnCAdaonw4J.

[Mayer, Jonathan]

Hi all,

 

I’m a bit late to the Jira 5 party but it looks like we’re going to be upgrading in the next few months too.

 

I was wondering whether people who have updated to Jira 5 have found that the features that this plugin offered are replicated either in the core REST functionality? Or did anyone do any work to refit the webservice to work with Jira 5 in the end?

 

I have quite a collection of tools which use SOAP to connect and interact with Jira, several of which rely on the functionality of this webservice. I’m trying to work out what direction to take – to stick with SOAP for the time being and use a modified version of this plugin, or whether to jump into using REST in the hope that the code changes aren’t too bad and the functionality I need is available.

 

Anyone got any words of wisdom to add from their own experience?

 

Thanks,

Jon.

--

[Isaac Johnson]

Since going to JIRA 5 I've been redoing all my webapps to REST from SOAP. I've not found a need for this pluggin.  i can send you some samples if you like. REST returns a much more complete object (e.g. No more having to query the statuses seperatly ).  All my stuff is in perl so Im not sure what other languages are going to be like switching; perl was pretty straightforward

[Mayer, Jonathan]

Thanks Issac. I’ll be using PHP but seeing your samples would be helpful.

 

Cheers,

Jon.