If we take a look at the Frontend Script configuration and compare it with our Media Type, that’s when it gets interesting: Looking at the Media Type we have our Parameters and the Javascript script. The Jira ServiceDesk default Media Type is of course already set up, but that’s not the most interesting part – although super useful nevertheless.
If we look at the particular Zabbix Media Type, we can see something interesting. Now once you have set up everything on the Jira (or which ever other service desk you use) side, we can continue with the next step which is setting up the Frontend script. Make sure to save the API token somewhere, as you can only copy it over once. Check out the Project Settings -> Request types and use the number in the URL for the request type you’d like to use.
Jira Service Desk is already available though, meaning we can use the settings pre-defined in Zabbix. If not, you can always use a community solution or build your own integration. You can check out to see if the service desk system of your choosing is already available out of the box. To make the frontend script work we are going to need a working integration (Media Type in Zabbix terminology).
AWS JIRA TICKET CREATOR FREE
Feel free to apply this technique to any service desk system out there though, as we are definitely not limited to Jira Service Desk. Why? Simply because personally I am a big fan of the Atlassian product suite and it’s what I had available on hand.
AWS JIRA TICKET CREATOR HOW TO
How to Setting up JiraĪs mentioned, in this example we’ll use Jira. Let’s check take a look at how we can achieve this.
0 kommentar(er)
