Use Case:
In our company we have different areas that work across JIRA tasks and Confluence.
Sometime we need to set around 20 tasks for a common target. This tasks are for example to get up and running some customizations from our customers.
In the example that i'm going to use we need:
- [1] Epic Task
- [4-5] Main Tasks for the different areas
- [4-5] Sub-tasks from each main task
- Relate the task to labels
- Relate the tasks between them
- Attach links (Zendesk, Confluence, docs, etc)
This actions at this moment are executed by one person, but sometimes you forget to do a task, or may be creation the relations between tasks (blocks, relates to). With this we avoid human mistakes, we set the structure and then the script auto-generates all the tasks.
diegonalvarez
/
jira-workflow-tasks
Jira workflow tasks
JIRA Workflow tasks
This project allows to you create a workflow template to build tasks in Jira. You only need to set the specifications in multiples YML files, and then the script will generate the tasks and their relationships accordingly the YML configuration.
Requirements
This project uses two libraries:
This libraries are already loaded with composer
Getting Started
To get started it's necessary set some environment variables. You need to copy the .env.example file as .env file.
Here set the JIRA properties:
JIRA_HOST="https://your-jira.host.com"
JIRA_USER="jira-username"
JIRA_PASS="jira-password-OR-api-token"
Installing
Firts install composer to get the libraries installed.
composer install
Now it's necessary set the templates
Templates
The project already becomes with a example template. The templates are stored in the folder templates.
Template Folder
To get a project working you can copy and paste the structure of templates/example or create your own
First create a folder inside …
So with this we can set many templates in the projects folder and run automated workflows.
Top comments (1)
Great post on using YAML files to create JIRA workflows! It's impressive how YAML can simplify the process of defining tasks and automating workflows, making it easier for teams to manage their projects effectively.
In my experience, leveraging YAML for JIRA workflows not only enhances clarity but also allows for version control, which is crucial when multiple team members are involved. I’ve found that maintaining a repository of YAML files for different workflows helps in quickly adapting to changes and ensuring consistency across projects. Additionally, integrating these YAML configurations with CI/CD pipelines can further streamline the deployment of updates.
For those exploring alternatives to JIRA or looking to enhance their project management experience, I recently came across a helpful resource that discusses some of the best JIRA alternatives. It might provide insights into different tools that can complement or replace JIRA workflows effectively: blog on JIRA alternatives.
What are some of the challenges you've faced when implementing YAML workflows in JIRA? I’d love to hear your thoughts and experiences!