JIRA plugin - SOAP connectivity deprecated in favour of REST api

Description

Hi,

Atlassian deprecated SOAP functionality, which was used by the upload to jira plugin in Greenshot.

https://developer.atlassian.com/jiradev/jira-apis/jira-api-status/jira-rpc-services/jira-xml-rpc-overview/soap-and-xml-rpc-api-deprecation-notice

I now get a 404 error with the same greenshot jira plugin configuration I was using before.

Environment

Win 8 - Greenshot 1.2.6 Build 7 (64 Bit)

Attachments

1
  • 19 Aug 2015, 02:35 PM

Gliffy Diagrams

Activity

Show:

Robin Krom September 16, 2016 at 6:56 PM

The JIRA plugin seems to work again, I even added SVG support.
Closing this ticket, to be able to start working the release process.

Release candidates will be coming soon.

Robin Krom August 19, 2016 at 9:35 AM

The problem with the configuration was that you used 1.3. The dutch was no problem, I am dutch slightly smiling face

For the others that follow this, the URL "should" be converted automatically to the correct one... if this is not the case, let me know.

Robin Krom August 18, 2016 at 2:57 PM

Please send your greenshot.log to getgreenshot@gmail.com, I couldn't find the issue belonging to the config-reset so quickly.

http://getgreenshot.org/faq/where-can-i-find-greenshots-log-file/

Jelle.Koster@kewill.com August 18, 2016 at 10:20 AM

@Robin: OK. Is there any logging I could provide?

Robin Krom August 18, 2016 at 9:52 AM
Edited

There is a bug in Greenshot which we never really found, due to the lack of reporting people (we made changes to test, but nobody reported back), where the configuration is reset. This *might *have been the case, we don't know when it happens. In the next Greenshot version (not 1.2) this will be fixed as I rewrote the configuration part completely.
I can't find another reason for why the Uri was gone disappointed face

In the mean time I am just going through my changes to check if there is anything to make it more stable, and I have added a small improvement (not yet available to test):
The previously used Jiras, shown in the dynamic destination picker (the menu shown after a screenshot), will have a different icon depending on the issue type (task, error etc). This is retrieved automatically from the JIRA system, and cached for a while. I will also check if this is possible in the form, but don't want to make a lot of changes... that will be for newer version.

Fixed

Details

Assignee

Reporter

Affects versions

Components

Priority

Labels

Time tracking

2w 3d logged

Sprint

Created August 19, 2015 at 2:36 PM
Updated October 2, 2016 at 7:48 PM
Resolved August 17, 2016 at 1:17 PM