How do I link my JIRA development stories to Service Desk "change" tickets?

[Thomas Sanza]

When we've finished development of a series of stories and ready to release to Production, we want to be able to create a "change management" ticket in Service Desk to record the changes with links to the specific stories being promoted. How can I do this through the customer portal?

[John D Patton]

One way would be to fire off a webhook to post an update 

https://developer.atlassian.com/jiradev/jira-applications/jira-service-desk/jira-service-desk-webhooks

https://confluence.atlassian.com/servicedeskcloud/automating-your-service-desk-732528900.html

[Thomas Sanza]

Does your organization use Service Desk for it's Change Management process? Is that what you do? We're trying to implement a new, more efficient, process than what we have now so I'm trying to understand if JIRA SD is a good option for us.

[Itamar Ben Sinai]

Hi

Why through customer portal? Are these  2 different jira instances? 

[Thomas Sanza]

JIRA Service Desk is licensed separately from JIRA so I'm trying to avoid paying for both licenses for the entire staff.

Our developers, QA and Business Systems Analysts are all in JIRA. Once stories are completed and ready for release to Production, I'm looking for an efficient way to group them into a Change Management request.

The online documentation does not address how to do this. Am I missing something?