Hello
I am trying to create JIRA issues form an external application by calling the following URL:
https://HOSTNAME/jira/secure/CreateIssueDetails!init.jspa?pid=PID&issuetype=ISSUETYPE&&toggle=true&priority=PRIO&fixVersions=FIXVERSION&components=COMPOENENT&assignee=ASSIGNEE&issuelinks-linktype=relates%20to&issuelinks-issues=CDE-379
In addition to the standard parameters, I am passing a type of relation (in this case "relates to") and the issue which the one being created is relating to (in this case CDE-379).
The previous URL is working fine when I entered a value in issuelinks-issues which does not exist, so if in the example above, the issue CDE-379 does not exist in JIRA, then the field Linked issues is prepopulated with '"Relates to" and the field issue with "CDE-379". I can also see a message saying that issue does not exist which obviously is fine.
On the other side, if issue CDE-379 exists, the field "Linked issues"is not updated with the value sent in the URL and remain as "blocks" and the field "Issue" is not updated and remains empty.
How could I solve this problem ?.
Thank you for your help
Regards,
Luis
By using the well-defined REST API for server... You will not be able to cover all specific cases without using the Jira webservice:
https://docs.atlassian.com/software/jira/docs/api/REST/7.12.3/
Hello, thank you for your answer. I will check the REST API.
One question, as I said, if I enter an issue which does not exist in JIRA, all fields are correctly updated. It fails, only when the issue exist in JIRA. Why is it behaving like this ?. Am I doing something wrong or is it a bug on confluence ?. I will check the RESP API, but would like to know the reason of this behaviour.
Thank you in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.