Learn how to set up Jira to use Jira for Workflows . After this setup, you can start using Jira for Workflows actions in your workflow.
app-engine:apps:install
permission.To use Jira for Workflows actions, you first need to install it from Dynatrace Hub.
After you install Jira for Workflows, you need to perform some initial steps to set up the connection between Jira and your Dynatrace environment.
Create a Jira connection
Configure EdgeConnect
Grant permissions to Workflows
Authorize connection to Jira
*.atlassian.net
can be added if the Jira for Workflows actions should connect to a Jira Cloud instance.This way, you can granularly control the web services to which your Dynatrace environment can connect.
If you are connecting to a self-hosted Jira instance, you might require EdgeConnect to establish a connection behind your firewall.
Some permissions are required by Workflows to run actions on your behalf.
To fine-tune permissions granted to Workflows
app-settings:objects:read
state:app-states:read
state:app-states:write
state:app-states:delete
For more on general Workflows user permissions, see User permissions for workflows.
Basic Authentication
We don't recommend using the basic authentication scheme, but it may still be required to authenticate older Jira Server versions that don't support the personal access token.
Personal Access Token (PAT) recommended
This is the recommended method to use for Jira Server. To learn which versions of Jira Server support personal access tokens and how you can create them, see Using personal access tokens in the Atlassian Jira documentation.
Jira API Token (Jira Cloud)
When connecting to a Jira Cloud instance, use the Jira API tokens.
To improve traceability and audibility, use a Jira service user to access your Jira instance.
To add connection settings, you need the following permissions:
ALLOW settings:objects:read, settings:objects:write, settings:schemas:read WHERE settings:schemaId = "app:dynatrace.jira:connection"
For details, see Permissions and access.
Be aware that connections are shared and can be used by all users with app-settings
read permissions. This is by design, as workflows enable a simplified ticket lifecycle across projects and entities.