Automating Jira – 3 Examples Using Automation for Jira

Automating Jira – 3 Examples Using Automation for Jira

As Atlassian Experts and Solution Partner, Ascend Integrated uses many add-ons (apps) for implementing complex business requirements and scenarios. These add-ons / apps provide the ability to extend Jira further, either by adding scripts or configurations to meet evolving business needs. One add-on / app we’ve used with multiple clients to solve issues effectively and efficiently is Automation for Jira. Automation for Jira frees your team to focus on what’s important: development and releasing shippable products and serving your customers. With limited scripting, you can get a full automation suite up and running. The app relies on Rules set up in a “When”, “If”, and “Then” structure. For instance, “When: Value changes for Field X, if field x = “Updated”, Then: Edit issue fields”. In this blog, we wanted to share with you 3 unique ways to automate your Jira instance using the Automation for Jira app.

Updating Read-Only Fields

Setting a read-only field in Jira is easy. You can view the Community answer here: If you’d like a read-only field value to update based on the values of other fields, Automation for Jira can accomplish this efficiently. Check out the configurations below:
  • When: “Value changes for” rule (Be sure to select the “Execute this rule immediately…” option)
  • If: set the JQL pointing to a specific field (i.e. Priority)
  • Then: “Edit Issue Fields” to choose which fields to edit. (This would be a read-only field for the users. Users will not be able to manually set this field, it will automatically set based on JQL parameters.)
An example of how this rule will be set up is shown below:

Combine with Dynamic Forms

Dynamic Forms another fan favorite, provides the ability for fields to display dependent upon selected values. While Dynamic Forms fields do not work directly with Automation for Jira, you can have other fields update based on a Dynamic Forms Field’s value through JQL. To do this, set up the following:
  • When: “Value changes for” rule
  • If: set the JQL pointing to the Dynamic Form field
  • Then: “Edit Issue Fields” to choose which field(s) to edit.

Managing Service Desk Tickets

If a user finds a verified bug, and they log it into Service Desk, Automation Jira can automatically create a cloned issue in your Jira development project, without agent intervention. To accomplish this, simply add a rule like the set up below:
  • When: “Issue Created” rule
  • If: set the JQL pointing to the field (i.e. customfield1000 = “X”)
  • Then: “Create Issue” and select what values should be in the fields.
This ensures both the development and agent queue for specific bugs / issues are always in alignment. Interested in checking out the app? Download it from the Marketplace here. It is available for Cloud, Server, and Data Center. Have questions about building out automation in Jira? Reach us here. How have you used automation in Jira?
Jira’s Scalability: What to Expect

Jira’s Scalability: What to Expect

As 2017 came to a close our team at Ascend Integrated asked ourselves a simple question: How does the Jira ecosystem exist within a small team? As many project management solutions have gone all-in on Enterprise solutions, Atlassian has maintained that Jira is prime for small teams while also possessing supreme scalability through the SAFe methodology within Jira. In this blog, we’ll explore how small teams can utilize Jira to its fullest extent.


One of the most important features that make Jira small-team-friendly is cost. As many agile teams look to transition from the sticky-note on the whiteboard phase over to a project management tool, cost becomes a major factor. The cost for the cloud instance of Jira for 1-10 users is only $10 per month. Plus, adding users is quite easy and will cost you an additional $7 per user up to 100 users. As your team grows, your cost per user actually decreases. We would also recommend you go with annual pricing if you know that you will be using Jira for the foreseeable future.


Agile teams need the ability to work with speed, cohesiveness, and autonomy within the context of a single platform. Jumping between different project management tools wastes time and can cause confusion between departments. With Jira as your central hub, you have the ability to connect to products like Confluence and BitBucket. Jira’s seamless integration with these tools will allow your team to store development documentation, decompose team silos through open communication, and track development issues throughout the development lifecycle. Working with project managers, back-end engineers, and designers has never been easier thanks to these integrations.


We’ve discussed price and flexibility, including two great integrations with Confluence and Bitbucket, but how does Jira itself standout from a user perspective? Jira’s custom workflows, JQL functionality, and personalized Kanban and SCRUM boards allow for members from all teams and skill levels to utilize Jira in a way that best suits their team while simultaneously tying back to the same projects. The beauty of Jira is that you can make it as simple or complex as your team needs, meaning once you of understanding vast amounts of customization at your disposal, you have complete autonomy over your workflows, visualizations, and tracking initiatives.

The Case for Collaboration

Jira certainly isn’t the only project management tool with flexibility and scaling ability, however, it is the best tool currently available with added documentation and repository integrations and some serious out-of-the-box usability for a small-team budget. If your team is looking for a low-risk project management solution to start off the new year, then we strongly suggest giving Jira a try!