[
https://issues.apache.org/jira/browse/CONNECTORS-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17553253#comment-17553253
]
Karl Wright commented on CONNECTORS-1713:
-----------------------------------------
[~schuch], the SharePoint connector requires configuration information that
specifies the version you're trying to talk to. But that's because there isn't
a version interrogation present in the API for SharePoint. If there is such a
capability for Jira I'd see how difficult it would be to use it. The version
information should ideally be retrieved during the connect() method, and thus
stored as an instance variable for the connector. Make sure you clean it out
again when disconnect() is called though to prevent a pooled instance from
malfunctioning.
> 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)
