---
title: "Groovy Console"
canonical: "https://support.appfire.com/space/JMWE/462094373/Groovy%20Console"
format: markdown
---
> Macro (aura-html)

This page allows you to run Groovy scripts against Jira issues without needing to edit a workflow transition. Navigate to the page using **Jira Administration → Manage apps → Groovy Console**. 

![image](media://3f7e1c7d-7413-4907-be0b-7ee3001b73ee)

Perform the following:

1. **Type**: Select one of the following options:
  - **Groovy Script**: Select this option to use *Groovy Script* as input. For more information, refer to [Variables and functions used in a Groovy expression](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461799437).
  - **Groovy Template**: Select this option to use *Groovy Template* as input. For more information, refer to [Groovy templates](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461930609).
2. **Groovy script**: Enter a Groovy script or template depending on the **Type **selected. For more information on how to use this editor, refer to [Groovy Editor in JMWE](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461897846).  
To test the input:
  1. Click `Test Groovy Script` or `Test Groovy Template` to navigate to the **Test Groovy Script** or **Test Groovy Template** window respectively, where you can select Jira issues.
  2. Select the **Issue key **and/or optionally **Linked issue key**, **Parent issue key **to select the issue on which the Groovy input is run. You can also click `Select issue` to navigate to **Issue selector** to select an issue.
  3. Click `Test` to verify if your script (or template) runs successfully or not.  
For more information, refer to [Groovy script tester in JMWE](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461766715).

> ⚠️ Ensure the Groovy script or template inserted into the editor matches the **Type **selected. If not, a warning message is displayed notifying you to modify the input type.