You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/03 10:45:00 UTC

[jira] [Updated] (CAMEL-17348) camel-jira component newIssue does not work across multiple projects

     [ https://issues.apache.org/jira/browse/CAMEL-17348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-17348:
--------------------------------
    Fix Version/s: 3.x

> camel-jira component newIssue does not work across multiple projects
> --------------------------------------------------------------------
>
>                 Key: CAMEL-17348
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17348
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jira
>    Affects Versions: 3.14.0
>            Reporter: Zachary Gutterman
>            Priority: Minor
>             Fix For: 3.x
>
>         Attachments: Screen Shot 2021-12-16 at 10.52.10 AM.png
>
>
> The camel-Jira newIssue endpoint depends on Jira's sorting by id to find the most recent issue. Jira sort by id, however, does not sort across all projects and is not a reliable way to return a list of newest issues. (See attached screenshot of sorted issues by id desc with endpoint [/rest/api/latest/search?jql=ORDER+BY+id+desc|https://zachtestjira.atlassian.net/rest/api/latest/search?jql=ORDER+BY+id+desc].) A solution could use the "created" field instead which reliably returns issues by most recent.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)