Jira

In more serious development environments, Jira stands out as a standard tool due to the ease of initial configuration and quick startup. Setting up Jira is easy, allowing teams to get started with minimal hassle. Moreover, its high configurability is a key factor that allows teams to adapt workflows and processes to specific needs. Jira stands out as a preferred choice for teams, including ours, involved in advanced development practices. Its flexibility serves as a dependable foundation for effective project management and seamless collaboration.

Jira automation

Jira ticket automation enables seamless integration with GitLab branches, allowing for automated status updates based on branch status changes. By linking Jira tickets to corresponding branches in GitLab, teams can establish rules and triggers to automatically update the ticket status as the branch status evolves. For example, when a branch is created or merged, the associated Jira ticket status can be automatically updated to reflect the corresponding stage of development or deployment. This automation streamlines the workflow by eliminating manual status updates, ensuring that ticket statuses accurately reflect the progress of related development activities. It enhances collaboration between Jira and GitLab, providing teams with real-time visibility into the status of their development work and facilitating efficient project management.

In our workflow, we leverage three key automations to seamlessly manage Jira ticket statuses in response to GitLab branch and pull request activities. Firstly, when a new branch is created, we automate the transition of the associated Jira issue to IN PROGRESS, signaling the start of development work. Secondly, upon the creation of a pull request, our automation promptly moves the corresponding Jira issue to CODE REVIEW, indicating that the code changes are ready for review and evaluation. Finally, upon successful merging of the pull request, the automation completes the lifecycle by transitioning the Jira issue to DONE, marking the completion of the development task. These automations ensure that our Jira tickets accurately reflect the progress of our development efforts, facilitating smooth collaboration and efficient project tracking.

Step by step configuration

Navigate to the sidebar and select Project settings under the desired working project.
In the project settings menu, click on Automation in the left sidebar.
Choose whether to select a pre-defined template or create a custom rule based on your automation requirements.
Begin configuring your automation rule by defining the triggering conditions. Specify when the automation will be triggered, such as when an issue is created, updated, or transitioned.
Next, specify the operation that must match the triggering conditions. This could include specific issue fields, status changes, or other criteria.
Finally, define the actions that will occur after the rule is triggered. This could involve transitioning the issue status, sending notifications, or performing other automated tasks.

Permission required

Note that users responsible for configuring automation rules must have appropriate permissions within the project to effectively create and manage these rules.

PreviousMaven NextConfluence documentation

Last updated 8 months ago

Jira automation

Step by step configuration

Navigate to the sidebar and select Project settings under the desired working project.

In the project settings menu, click on Automation in the left sidebar.

Choose whether to select a pre-defined template or create a custom rule based on your automation requirements.

Begin configuring your automation rule by defining the triggering conditions. Specify when the automation will be triggered, such as when an issue is created, updated, or transitioned.

Next, specify the operation that must match the triggering conditions. This could include specific issue fields, status changes, or other criteria.

Finally, define the actions that will occur after the rule is triggered. This could involve transitioning the issue status, sending notifications, or performing other automated tasks.

Permission required

Note that users responsible for configuring automation rules must have appropriate permissions within the project to effectively create and manage these rules.