[
https://issues.apache.org/jira/browse/CONNECTORS-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127039#comment-14127039
]
Karl Wright commented on CONNECTORS-1026:
-----------------------------------------
Hi Daniel,
I'd be concerned about whether protocol://HOST for rest is the same as
protocol://HOST for a direct issuekey ticket access. If you can do enough
research to be certain that this is not a problem, I have no difficulty
changing the connector to use the primary ticket URL instead of the self field
URL. Unfortunately my resources for delving into Jira possibilities and
configurations is quite limited at this time, so it is up to you to determine
if this is safe.
> ID/URI used in JIRA Connector
> ------------------------------
>
> Key: CONNECTORS-1026
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1026
> Project: ManifoldCF
> Issue Type: Improvement
> Components: JIRA connector
> Affects Versions: ManifoldCF 1.7
> Reporter: Daniel Aschauer
>
> Currently the id of the solr document is the "self" field that comes from the
> REST API and has the form http://HOST/rest/api/2/issue/ISSUEID
> At least in our project we would like to use the "real human-readable"
> url of the issue (not the rest json formatted). (e.g. http://HOST/ISSUEKEY)
> - What do others think about it?
> - As it doesn't seem that this url can be retrieved anyhow in the API, I
> guess it has to be composed, Would the mentioned form http://HOST/ISSUEKEY
> always work?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
