Maven 1.x JIRA Plugin

Plugin uses deprecated API to retrieve JIRA issues

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.2
  • Fix Version/s: 1.3
  • Labels:
    None
  • Environment:
    JIRA 3.4.1-#107
  • Number of attachments :
    0

Description

Jira is logging errors about a client accessing a deprecated API. We think the JIRA plugin is causing this:

INFO: 2006-01-12 23:56:31,125 WARN [jira.util.retro.InvalidParamLogger] DEPRECATED. Deprecated parameters called for URL '/secure/IssueNavigator.jspa?view=rss&pid=10001&statusIds=1&status=3&status=4&resolution=-1&sorter/field=created&sorter/order=DESC&sorter/field=priority&sorter/order=DESC&tempMax=1000&reset=true&decorator=none' from remote user with ip address ............. They should be informed that their bookmark has been deprecated and should be updated.

It seems a new API is available ?

Activity

Hide
Permalink
Lukas Theussl added a comment -

Indeed, the maven-jira-plugin uses the parameters 'resolutionIds', 'priorityIds' and 'statusIds', which have been deprecated in JIRA 3.3 (http://confluence.atlassian.com/display/JIRA/Parameter+changes+in+Issue+Navigator).

I will look into it.

Show
Lukas Theussl added a comment - Indeed, the maven-jira-plugin uses the parameters 'resolutionIds', 'priorityIds' and 'statusIds', which have been deprecated in JIRA 3.3 ( http://confluence.atlassian.com/display/JIRA/Parameter+changes+in+Issue+Navigator ). I will look into it.

People

  • Assignee:
    Lukas Theussl
    Reporter:
    Silvester van der Bijl
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: