[ 
https://issues.apache.org/jira/browse/CONNECTORS-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552585#comment-17552585
 ] 

Markus Schuch edited comment on CONNECTORS-1713 at 6/10/22 6:40 AM:
--------------------------------------------------------------------

With CONNECTORS-1493 we have already experienced the situation the other way 
round. Here we had to put the quotes in the query to make it still work.

[~kwri...@metacarta.com] are you okay with me adjusting the query to adapt to 
JIRA Server Versions (8.20+) and thus no longer support older versions?


was (Author: schuchm):
With CONNECTORS-1493 we have already experienced the situation the other way 
round. Here we had to put the quotes in the query to make it still work.

[~kwri...@metacarta.com] are you okay with me adjusting the query to adapt to 
JIRA Server Versions? (8.20+)

> JIRA Repository Connector ignores issue security when ingesting from JIRA 
> 8.20+
> -------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-1713
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1713
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: JIRA connector
>    Affects Versions: ManifoldCF 2.22
>            Reporter: Markus Schuch
>            Priority: Major
>         Attachments: api-docs.png
>
>
> There was obviously a change in the behaviour of the JIRA Server REST API:
> The {{GET /rest/user/viewissue/search}} has a parameter {{username}}.
> In JIRA 8.13.x the value must be to double quotes ({{username=""}}) to fetch 
> all users that have browse permission for the issue.
> In JIRA 8.20.x the value must be empty ({{username=}}).
> I found no information about this change in the JIRA Release Notes.
> I raised a question in the Atlassian Dev Community:
> https://community.developer.atlassian.com/t/rest-api-change-in-behaviour-of-find-users-with-browse-permission-get-rest-user-viewissue-search/58819



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to