Page tree
Skip to end of metadata
Go to start of metadata

Enjoy your stay mate!

We at Rixter are continuously working on delivering the best products on the market to make your day to day tasks as easy as possibly, whether you are an admin, user or any other role.

Checkout our products in the list below.


Inbox for JIRA delivers world-class in-app notifications on issue events inside JIRA. You will be instantly notified when something happens that relates to you or that you are interested in watching.

In-app notifications that you need inside of JIRA. With multi-language support and intuitive users interface.



Inbox for JIRA


Get it direct on Atlassian Marketplace here Inbox: in-app notifications for Jira



Integration Hub for JIRA


Get it today on the Atlassian marketplace: Integration Hub for JIRA


Do you have any questions or in need of support then feel free to use our first class support via the portal: Rixter Support Portal

Bug Tracking

For checking open bugs or planned work, have a look at Rixter Open Bug Tracker

With our latest release of REST Integrations & Automations, it is super simple to create any OAuth integration without needing to code!

In this tutorial, I will describe how to do it with salesforce and some of the use cases that we see are common.

So we want to achieve this:

When an issue is created it sends that to Salesforce and updates the issue with the case number and status.

Secondly, we want to fetch the status of the case to find out if there has been any update. 

This can also be done on a periodic schedule by using the cron expression. (not covered in this article)

So were do we start?...

The first thing that needs to be done is to create what Salesforce calls a Connected app.

The important thing here is to select the right scope and to add the callback URL. This is always found on the OAuth authentication page in RINT.

Once this is done the next step is to set up the authentication in RINT.

In RINT we select the Authentication menu (lock icon) and enter the details that out Salesforce connected app returned. 

Note that state shall be check but leave the scope blank.

Once all the data is filled in click Authenticate and login to Salesforce. You will notice the two labels "Auth Code Granted" and "Access Token Granted" when all went good.

So now down to the actual REST call to do something in Salesforce based on JIRA data

Simply click Create and fill in a name and select the application / json as template to get the headers for free.

The request details can now be filled in, such as the method and url. Note for salesforce use the "" as url and not the

Now to where the actual JIRA data comes from

The body part of the form describes what data to send, RINT can send the issue data by simply using curly brackets and dot notation.




Trigger Time!

Once the data for the REST call is setup the only thing left is to add a Trigger to decide when to send the call.

We will use Issue Created with the condition limited to our SAL project.

This now means that the REST call to salesforce using the authentication that we setup will be triggered every time there is a new issue in our SAL project!

Yeah! but wait... how does it know to update the issue with the Case ID?

Now the chained actions come into play.

We will create a new action again this time we will use the "Select parent action" field to specify our previously created "Salesforce - Add case info"

Further on we can take some help by selecting the "JIRA Core Server" category and the "Edit Issue" template to speed things up.


What did we get now?

First, we can see that the tree now has a parent → Child for the salesforce part. Secondly, we can see that it created a new REST request to our JIRA server.

By selecting "Auto-generate 1st level as variables from parent response" we will automatically on this REST call get the response from the create case call as variables.

The response can be viewed by clicking on the Execution log on the "Salesforce - Add case info" action

So let's use what we know from the response to send that to the edit issue REST call.

As noted the {{id}} will automatically be replaced by the response from the parent once the chain is executed.

Inbox new feature teaser!

Can you spot the new Inbox for JIRA feature?

Are you switching between your mailbox and JIRA to keep up to date with what is happening?

Are you feeling that important issues are some times missed out?

Time to change that!

According to different studies, context switching can eat up to 40-80% of your productive time!!!

With Inbox for JIRA you can increase your productivity and remove the barriers by adding in-app notifications!

Inbox is located next to your avatar and is shown as a bell.

Get it today at Atlassian Marketplace Inbox for JIRA


There's a new add-on in town! "REST integrations and automation for Jira" made by the add-on vendor Rixter.

REST integrations and automation for Jira enables custom made, no-code trigger-driven rest-integrations and automation.

During the engineering research, people have said: "This is the missing piece we've been looking for!".

So, what's the fuzz all about?

This addon gives you the power to create REST integrations and automation from an intuitive UI; no-code and scriptless. Triggered by an issue event or on a scheduled basis, all in the world of REST API's.

All your REST-integrations aka. "actions" can be chained, using the response from one as input to the next. Hence, the possibilities are endless!

The fact that Jira is exposing a REST API's this becomes extremely powerful, you can now automate your Jira instance in any way you want.

REST integrations and automation for Jira can be found at the Atlassian marketplace. Click here to Get it now!

Read more:

Happy integrations!