Great question! AM Utils simplifies your daily Jira operations by offering you additional conditions, validators, post-, and JQL functions. These features expedite work within Jira, and add powerful workflow extensions for every Jira admin.






We’re frequently asked to help with the automation of certain routine tasks. While the remedies are usually some set of features, we’ve seen that most of these challenges across multiple organizations are quite often the same.






Such as:

  1. You’ve searched for a solution to eliminating wasted time by automating as many of the routine operations as possible.
  2. Where’s the solution that won’t drain your budget when you only need certain features? You don’t want to buy full-blown and pricy solutions, like ScriptRunner, or many single-purpose apps.
  3. Many processes in your Jira steal a lot of your attention, and you need something on hand to reinforce them in your Jira so you have a clean backlog.

To our Jira Admins managing instances and Project Managers building business processes, doesn’t this all sound familiar?  We know that you’ve heard these stories countless times. But luckily, you’ve found that AM Utils is a great resource for solving all of that.



Validators – help check various conditions and input criteria. Use regex, JQL, links, comments validators, and more.

Post-functions – enable you to automate routine tasks, and help you perform tasks such as copying a value from a custom field, cloning, assigning tickets based on a certain condition, and more.

JQL functions – customize searches to help you find tickets that have links, comments, subtasks and parents; commented by a specific user at certain times, or transitioned with certain conditions, and so on.





Perform any custom check-in your Jira. Here’s some inspiration for you:

  • Use the Comment Validator to require all users except those in the Jira-developers group to comment on a ticket when they transition it. This reinforces the need for people to provide context for their teammates so everyone’s on the same page.
  • Track down issues with the same summary, and keep your backlog clean with the JQL Validator.
  • Regex Validator helps to ensure that a team only enters integer numbers in your Estimate custom field.



Utilize the following verifications to meet your needs:

  • Limit the number of tickets that your team members are working on at any time by setting a particular status for your users.
  • See to it that that important ticket from Design with the latest assets or a deck has all the attachments required.
  • Ensure that your tickets have all the links in place by placing an additional condition for checking this.



Adopt these functions in your day to day activities:

  • You have Jane the developer and Mark the QA. Once Mark is ready with his tests and provides feedback, he returns the ticket from Testing to Development for the final tweaks. You can set up a post-function to avoid extra clicks, and assign the ticket back to Jane as soon as the ticket is transitioned back to Development.
  • When a Project Lead needs to verify that a complex feature is finally Done by Jane the developer, you can set up a post-function that assigns the ticket to the user from a custom field which is a Project name. Then this will automatically be assigned to the Project Lead.
  • Sometimes, you use additional plugins to know how long a certain issue was in particular status such as (Total Time in Status Field). Then you’d likely want to set up the Original Estimation field for the similar tickets in the next sprints as the time spent in Total time in Status. You can set up a post-function that lets you copy the value from Total Time in Status custom field to the Original Estimationfield.
  • Use the Issue Clone Post Function in times of when you want to easily clone an issue so that it’s super quick to create a new issue with a standardized set of fields while being transitioned.



Advanced searching will no longer be an issue:

  • The app will help you find tickets where a certain user (logged/ not logged) commented anything within the last X hours using userCommentedIssues or commentedIssues JQLs in no time.
  • These sets of functions empower you to:
    • get a list of tickets in the specified project that were in a certain status, X amount of times with a certain operation using transitionCount
    • find the users who are the members of a certain role inside the Jira project using transitionRole
    • get a list of issues where the status was changed by the specified user  to the specified status using transitionReporter 
    • find issues that were transitioned by anyone from the specified group to the specified status using transitionReporterGroup 
    • get a list of tickets for which the status was changed within the specified time frame to the specified status using transitionDate 

Users, like yourself, utilize the following functions for their day to day work:

  • issuesParents – Returns a list of issues that are parents of all issues inside the specified JQL query.
  • issuesSubtasks – The issuesSubtasks function returns a list of issues that are subtasks of all issues in the specified JQL query.
  • linkedIssuesHasStatuses – Returns tickets that have linked issues that are in the specified status and that are linked with the specified linking type.
  • relatedIssuesByField – Returns issues that contain issue keys of other issues in the specified field.
  • relatedIssuesByQuery – Allows applying Query2 for the Query1 results.

More features are coming in the near future. If you would like to request a feature – let us know!

Start solving your routine tasks now >


Tagged with: , , , , , , , , , , ,

Categorized in: , , , , , , , , ,