Skip Menu |

This queue is for tickets about the JIRA-Client-Automated CPAN distribution.

Report information
The Basics
Id: 120158
Status: resolved
Priority: 0/
Queue: JIRA-Client-Automated

People
Owner: FRIMICC [...] cpan.org
Requestors: Roy.Lyons [...] cmegroup.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 1.5



Subject: feature request: jira 7.x api compatibility
Date: Thu, 9 Feb 2017 15:26:14 +0000
To: "bug-JIRA-Client-Automated [...] rt.cpan.org" <bug-JIRA-Client-Automated [...] rt.cpan.org>
From: "Lyons, Roy" <Roy.Lyons [...] cmegroup.com>
We will be moving to 7.2.7 in 3 weeks, and I need to make calls that work with the new rest structure. I can rewrite everything to use bare rest, but I thought I would make a request to get a version of this module that would work as a drop-in replacement. Show quoted text
________________________________ NOTICE: This message, and any attachments, are for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at E-Communication Disclaimer<http://www.cmegroup.com/tools-information/communications/e-communication-disclaimer.html>. If you are not the intended recipient, please delete this message. CME Group and its subsidiaries reserve the right to monitor all email communications that occur on CME Group information systems.
JIRA::Client::Automated already works great with version 7+. I use it every day with the latest JIRA OnDemand cloud instance. This module has always only used REST API calls. Good luck with your upgrade! On Thu Feb 09 10:28:39 2017, Roy.Lyons@cmegroup.com wrote: Show quoted text
> We will be moving to 7.2.7 in 3 weeks, and I need to make calls that > work with the new rest structure. > > I can rewrite everything to use bare rest, but I thought I would make > a request to get a version of this module that would work as a drop-in > replacement. > ________________________________ > NOTICE: This message, and any attachments, are for the intended > recipient(s) only, may contain information that is privileged, > confidential and/or proprietary and subject to important terms and > conditions available at E-Communication > Disclaimer<http://www.cmegroup.com/tools-information/communications/e- > communication-disclaimer.html>. If you are not the intended recipient, > please delete this message. CME Group and its subsidiaries reserve the > right to monitor all email communications that occur on CME Group > information systems.