Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 

Story – A multinational organization uses Jira as a tool for Agile development and bug fixes. During hyper care/support phase multiple bugs are being reported. These bugs functionals explain to Technical teams and then create Jira one by one for each bug. There is no central mechanism which would collect issues/bugs and enhancements and create them on the fly. This RPA Bot attempts to do that. The BAs/Functional owners will list all the bugs and enhancements requests all in one single fixed excel workbook which they will keep on some drive. The Scheduled bot will check for the excel periodically and Jira will be created for those. If functional has listed down all kinds of story points then those story points can be created in Jira.

Captured Applications:

In this automation we will be capturing 2 applications. Login Screen and Screen which renders after logging in and once we log-in.

Login Application (Jira Application - Name)

Login Screen 1:


Userid element Declaration on Login Screen 1.

Password Screen:

Declaration of password element.

Here if you observe the both captured pages are essentially the same. Only difference is when first screen is loaded the screen DOM does not have password field. On click of submit then password field appears in screen DOM. An alternate to two screen captures could be one can load complete DOM of page and then declare elements accordingly. We will see this approach when we will automate creation of Jiras.

Your Work Jira Application

In this application we will capture screens and pop-up which comes after login into Jira.

After login to Jira, following screen shows up.

We only declare create button on this screen. We can proceed without declaration of create button as well and use keyboard shortcuts provided by Jira to procced further using keystroke (screen) activity of iRPA.

Click on create button on screen, a fragment shows up for creating Jira. On this screen we declare the necessary input fields to create a Jira. Thing to note here is we are not capturing a separate page we are using “Add Capture to Current Screen” option of already captured screen.

If we observe carefully, the create button which we declared previously is not throwing error even on capture of this pop-up, reason being iRPA framework is still able to identify the element from DOM. Also the element summary and description are visible as part of screenshot but the elements such as Assignee Field are not directly visible to declare them. Here we will use DOM to find elements in HTML page and map corresponding elements in iRPA.

e.g. to declare labels field in create Jira pop-up, we identify that html used tag is textarea and id for textarea is “labels-textarea”.

Now that we have identified id as text-area, we can turn to both/tree mode and search for identified id in element declaration of captured screen. Note that even the element is not visible on captured page image we identified and declared it using DOM.


Here, we login to app first, then read the excel content. Loop over excel content to create Jira one by one. The attached Workflow screenshots are self-explanatory. If everything goes as per plan you’ll see Jira created into system with details mentioned in Excel.

Note: This blog intended to showcase integration with Jira. There could be multiple scenarios possible with Jira.

More Information on web and other type of automation can be found at SAP iRPA Cloud Studio Guide

Cheers and Thanks!

Credits: I'd like to thank chintan for all the help and guidance he provided.
Labels in this area