jira-auto-tool 0.1.1

data/README.md

@@ -0,0 +1,159 @@
+# Jira::Sprint::Tool
+
+![Main Workflow - main branch](https://github.com/cbroult/jira-auto-tool/actions/workflows/main.yml/badge.svg?branch=main&label=Ruby%20-%20main%20branch)
+![Main Workflow - all branches](https://github.com/cbroult/jira-auto-tool/actions/workflows/main.yml/badge.svg?label=Ruby%20-%20all%20branches)
+
+****
+The purpose of this tool it support managing the sprints of multiple teams so it is easier to adjust to changes.
+See the [feature files](./features) for some behavior examples.
+
+## Warning
+
+1. You should familiarize yourself with this tool in a Jira sandbox project **before applying it to your context**. 
+That can be done easily by [creating a free Atlassian account](https://www.atlassian.com/software) 
+like it has been done to document [this tool features](./features) using executable specifications.
+
+1. Remember that you are **not allowed** to use confidential/sensitive information when familiarizing with this tool 
+in such a cloud sandbox. Though, if the sandbox belongs to the target context 
+(e.g., sandbox project on the client Jira instance) you can experiment with the parameters you intend to use later. 
+
+## Installation
+
+1. Install [Ruby](https://www.ruby-lang.org/en/downloads/).
+1. Install the gem...
+   * ... and add to the application's Gemfile by executing:
+
+     ```bash
+     bundle add UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
+     ```
+     
+   * ... if bundler is not being used to manage dependencies, by executing:
+     
+     ```bash
+     gem install UPDATE_WITH_YOUR_GEM_NAME_IMMEDIATELY_AFTER_RELEASE_TO_RUBYGEMS_ORG
+     ```
+
+## Setup
+
+While we strive to use convention over configuration as a principle, the following environment variables have to be set
+in order to use this tool:
+
+Required environment variables:
+
+- `JIRA_USERNAME` - Your Jira account username (e.g., "user@company.com").
+- `JIRA_API_TOKEN` - Your Jira API authentication token.
+- `JIRA_SITE_URL` - Base URL of your Jira instance (e.g., "https://your-domain.atlassian.net").
+- `JIRA_BOARD_NAME` - Name of the Jira board to work with (e.g., "Team Board").
+- `JIRA_BOARD_NAME_REGEX` - Regular expression pattern to match board names (e.g., "ART 16|unconventional board name").
+- `JIRA_PROJECT_KEY` - Key of the Jira project (e.g., "PROJ").
+- `JAT_TICKETS_FOR_TEAM_SPRINT_TICKET_DISPATCHER_JQL` - Query to identify tickets requiring sprint dispatching 
+(e.g., "project = PROJ AND Sprint IS EMPTY"). 
+See [Team Ticket Dispatching](./features/assign_tickets_to_team_sprints.feature).
+- `JIRA_SPRINT_FIELD_NAME` - Custom field name for Sprint (e.g., "Sprint").
+- `IMPLEMENTATION_TEAM_FIELD_NAME` - Custom field name for storing team assignments (e.g., "Implementation Team").
+
+Optional environment variables:
+
+- `ART_SPRINT_REGEX` - Can be used to limit the sprints that are going to be manipulated (e.g., "ART-16|(4\.1)"). 
+See [sprint filtering](./features/sprint_filtering.feature).
+- `JIRA_CONTEXT_PATH` - Context path for Jira instance (if needed typically "/jira").
+- `JIRA_HTTP_DEBUG` - Enable HTTP debug logging (set to "true" or "false").
+- `JAT_RATE_LIMIT` - Rate limit for Jira API calls (e.g., "1").
+- `JAT_RATE_INTERVAL` - Interval for rate limiting in seconds (e.g., "1").
+
+## Usage
+
+* Leverage the [specification by examples](./features)
+* Use the tool integrated help: 
+  ```bash
+  jira-auto-tool --help
+  ```
+* Usually the long option names have a short version equivalent to reduce typing.
+
+Below are a few examples.
+
+### Add Sprints
+
+The following is going to create sprints `sprint_prefix_25.4.3` until `sprint_prefix_25.4.6` 
+for the teams respective sprint prefixes. 
+```bash
+jira-auto-tool --sprint-add=25.4.3,4
+```
+
+### Align Time In Sprint Dates
+
+````bash
+jira-auto-tool --sprint-align-time-in-dates="14:15 UTC"
+````
+
+### List Sprints
+
+```bash
+jira-auto-tool --sprint-list
+```
+
+### List Sprint Prefixes (Teams)
+
+```bash
+jira-auto-tool --sprint-prefix-list
+```
+
+### Rename Sprints
+
+```bash
+jira-auto-tool --sprint-rename=25.3.5,25.4.1
+```
+
+### Team Sprint Mapping
+
+```bash
+jira-auto-tool --team-sprint-mapping-list
+```
+
+### Team Ticket Sprint Dispatching
+
+```bash
+jira-auto-tool --team-sprint-mapping-dispatch-tickets
+```
+
+## Development
+
+After checking out this repository.
+
+### Install Dependencies
+
+```bash
+bundle install
+```
+
+### Continuous Testing While Making Changes
+
+```bash
+bundle exec guard
+```
+
+### Experiment Using An Interactive Prompt
+
+```bash
+bin/console
+```
+ 
+### Install Locally
+
+To install this gem onto your local machine, run `bundle exec rake install`.
+
+### Release
+
+To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/cbroult/jira-auto-tool. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/jira-auto-tool/blob/master/CODE_OF_CONDUCT.md).
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the Jira::Sprint::Tool project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/jira-auto-tool/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,20 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+require "cucumber"
+require "cucumber/rake/task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+require "rubocop/rake_task"
+
+RuboCop::RakeTask.new(:rubocop) do |task|
+  task.options = ["--autocorrect"]
+end
+
+Cucumber::Rake::Task.new do |t|
+  t.profile = "rake"
+end
+
+task default: %i[rubocop spec cucumber]

data/bin/jira-auto-tool

@@ -0,0 +1,57 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+GEM_ROOT = File.expand_path("..", __dir__)
+LIBRARY_PATH = File.join(GEM_ROOT, "lib")
+$LOAD_PATH.unshift(LIBRARY_PATH)
+
+DEBUG = false
+
+if DEBUG
+  puts "GEM_ROOT: #{GEM_ROOT}"
+  puts "LIBRARY_PATH: #{LIBRARY_PATH}"
+  puts "$LOAD_PATH: #{$LOAD_PATH}"
+end
+
+require "bundler/setup"
+
+require "active_support/core_ext/object/blank"
+require "jira/auto/tool"
+require "jira/auto/tool/board_controller/options"
+require "jira/auto/tool/common_options"
+require "jira/auto/tool/config/options"
+require "jira/auto/tool/jira_http_options"
+require "jira/auto/tool/performer/options"
+require "jira/auto/tool/project/options"
+require "jira/auto/tool/sprint_controller/options"
+require "jira/auto/tool/team_sprint_prefix_mapper/options"
+
+require "optparse"
+require "optparse/date"
+
+tool = Jira::Auto::Tool.new
+
+option_parser = OptionParser.new do |parser|
+  Jira::Auto::Tool::CommonOptions.add(tool, parser)
+  Jira::Auto::Tool::JiraHttpOptions.add(tool, parser)
+  Jira::Auto::Tool::BoardController::Options.add(tool, parser)
+  Jira::Auto::Tool::Config::Options.add(tool, parser)
+  Jira::Auto::Tool::Project::Options.add(tool, parser)
+  Jira::Auto::Tool::Performer::Options.add(tool, parser)
+  Jira::Auto::Tool::SprintController::Options.add(tool, parser)
+  Jira::Auto::Tool::TeamSprintPrefixMapper::Options.add(tool, parser)
+end
+
+begin
+  option_parser.parse!
+rescue StandardError => e
+  error_message = <<~EOERROR_MESSAGE
+    #{e.class}: #{e.message}
+    #{e.backtrace.join("\n")}
+  EOERROR_MESSAGE
+
+  log.error { error_message }
+  warn error_message
+
+  exit 1
+end

data/bin/jira-auto-tool.bat

@@ -0,0 +1,2 @@
+@ECHO OFF
+ruby.exe "%~dpn0" %*

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/bin/setup-dev-win.bat

@@ -0,0 +1,3 @@
+
+
+choco install act-cli

data/cucumber.yml

@@ -0,0 +1,7 @@
+<%
+  default_tags = 'not @in-specification'
+  shared_args = "--publish-quiet --expand"
+%>
+default: <%= shared_args %> --format pretty --tags ' <%= default_tags %>'
+guard: <%= shared_args %> --format rerun --out rerun_failures.txt --format progress --tags ' <%= default_tags %>'
+rake: <%= shared_args %> --format progress --tags 'not @wip'

data/features/align_sprint_time_in_dates.feature

@@ -0,0 +1,33 @@
+Feature: Align sprint time in dates
+
+  Scenario: Align time in sprints having start and end dates
+    Given the board only has the following sprints:
+      | comment                            | name                   | length | start_date              | state  |
+      | should be unchanged because closed | Food_Supply_25.1.5     | 2-week | 2024-12-01 01:00:00 UTC | closed |
+      |                                    | Food_Delivery_25.1.2   | 2-week | 2024-12-14 18:00:00 UTC | future |
+      |                                    | Food_Delivery_25.1.3   | 2-week | 2024-12-28 18:00:00 UTC | future |
+      |                                    | Food_Restaurant_24.4.1 | 4-day  | 2024-12-05 23:00:00 UTC | future |
+      |                                    | Food_Restaurant_25.1.5 | 4-day  | 2024-12-09 23:00:00 UTC | future |
+      |                                    | Food_Market_25.3.2     | 4-day  | 2024-12-05 14:00:00 UTC | future |
+    When I successfully run `jira-auto-tool --sprint-align-time-in-dates="11:30 UTC"`
+    Then afterwards the board only has the following sprints:
+      | name                   | start_date              | end_date                | state  |
+      | Food_Supply_25.1.5     | 2024-12-01 01:00:00 UTC | 2024-12-15 01:00:00 UTC | closed |
+      | Food_Delivery_25.1.2   | 2024-12-14 11:30:00 UTC | 2024-12-28 11:30:00 UTC | future |
+      | Food_Delivery_25.1.3   | 2024-12-28 11:30:00 UTC | 2025-01-11 11:30:00 UTC | future |
+      | Food_Restaurant_24.4.1 | 2024-12-05 11:30:00 UTC | 2024-12-09 11:30:00 UTC | future |
+      | Food_Restaurant_25.1.5 | 2024-12-09 11:30:00 UTC | 2024-12-13 11:30:00 UTC | future |
+      | Food_Market_25.3.2     | 2024-12-05 11:30:00 UTC | 2024-12-09 11:30:00 UTC | future |
+
+  Scenario: Align time in sprints not having start and/or end dates
+    Given the board only has the following sprints:
+      | name                 | start_date              | end_date                | state  |
+      | Food_Supply_25.1.5   |                         |                         | future |
+      | Food_Delivery_25.1.2 | 2024-12-01 18:00:00 UTC |                         | future |
+      | Food_Delivery_25.1.3 |                         | 2024-12-01 18:00:00 UTC | future |
+    When I successfully run `jira-auto-tool --satid="14:15 UTC"`
+    Then afterwards the board only has the following sprints:
+      | name                 | start_date              | end_date                | state  |
+      | Food_Supply_25.1.5   |                         |                         | future |
+      | Food_Delivery_25.1.2 | 2024-12-01 14:15:00 UTC |                         | future |
+      | Food_Delivery_25.1.3 |                         | 2024-12-01 14:15:00 UTC | future |

data/features/assign_tickets_to_team_sprints.feature

@@ -0,0 +1,73 @@
+Feature: Assign tickets to team sprints as per an expected start date
+  In order to get some activities started by a team on a given date
+  As a product owner
+  I need the ability to automatically add those tickets to the corresponding sprints
+
+  Background:
+    Given a Jira Scrum board
+    And tickets on the board have an expected date field named "Expected Start"
+    And tickets on the board have a team field named "Implementation Team" with exactly those values:
+      | values       |
+      | A16 CRM      |
+      | A16 E2E-Test |
+      | A16 Logistic |
+      | A16 Platform |
+      | A16 Sys-Team |
+    And the board only has the following sprints:
+      | name                    | length | start_date              | state  |
+      | ART-16_CRM_24.4.1       | 2-week | 2024-12-01 11:00:00 UTC | closed |
+      | ART-16_CRM_24.4.2       | 2-week | 2024-12-15 11:00:00 UTC | active |
+      | ART-16_E2E-Test_24.4.1  | 4-day  | 2024-12-01 11:00:00 UTC | future |
+      | ART-16_E2E-Test_24.4.2  | 4-day  | 2024-12-05 11:00:00 UTC | future |
+      | ART-16_Platform_24.4.6  | 3-week | 2024-10-07 11:00:00 UTC | active |
+      | ART-16_Platform_24.4.7  | 3-week | 2024-10-07 11:00:00 UTC | future |
+      | ART-16_Sys-Team_24.4.12 | 1-week | 2024-12-24 11:00:00 UTC | future |
+      | ART-16_Sys-Team_24.4.13 | 1-week | 2024-12-31 11:00:00 UTC | future |
+      | ART-16_Sys-Team_25.1.1  | 1-week | 2025-01-07 11:00:00 UTC | future |
+    And the following environment variables are set:
+      | name                                              | value                                                |
+      | IMPLEMENTATION_TEAM_FIELD_NAME                    | Implementation Team                                  |
+      | EXPECTED_START_DATE_FIELD_NAME                    | Expected Start                                       |
+      | JIRA_SPRINT_FIELD_NAME                            | Sprint                                               |
+    And JAT_TICKETS_FOR_TEAM_SPRINT_TICKET_DISPATCHER_JQL has been defined as an environment variable
+    And the following tickets exist:
+      | summary                                                   | description                                                    | implementation_team | expected_start_date |
+      | ASX-1 - Prepare repository for CI/CD                      | start date is overdue => earliest sprint                       | A16 Sys-Team        | 2024-12-05          |
+      | ASX-2 - Implement stage deployment                        |                                                                | A16 Sys-Team        | 2024-12-26          |
+      | ASX-3 - Prepare L&P deployment                            | start expected on sprint last day => next one                  | A16 Sys-Team        | 2024-12-31          |
+      | ASX-4 - Implement prod deployment                         | starts mid sprint                                              | A16 Sys-Team        | 2025-01-01          |
+      | ASX-5 - Setup monitoring dashboard                        |                                                                | A16 Sys-Team        | 2025-01-07          |
+      | ASX-6 - Establish a solution wide holistic testing vision |                                                                | A16 E2E-Test        | 2024-12-04          |
+      | ASX-7 - Prepare an E2E Smoke Test in CI                   | no sprint available at that time, so going to stay sprint-less | A16 E2E-Test        | 2024-12-12          |
+
+  Scenario: List team to sprint prefix mappings
+    When I successfully run `jira-auto-tool --team-sprint-mapping-list`
+    Then the stdout should contain exactly:
+      """
+      +--------------------------------+
+      |      Team Sprint Mappings      |
+      +--------------+-----------------+
+      | Team         | Sprint Prefix   |
+      +--------------+-----------------+
+      | A16 E2E-Test | ART-16_E2E-Test |
+      | A16 Sys-Team | ART-16_Sys-Team |
+      +--------------+-----------------+
+      """
+
+  # TODO: fixme
+  @wip @failing-test
+  Scenario: Assign tickets to the relevant implementation team sprints as per the expected starts
+    When I successfully run `jira-auto-tool --team-sprint-mapping-dispatch-tickets`
+    Then the tickets should have been assigned to sprints as follows:
+      | summary                                                   | sprint                  |
+      | ASX-1 - Prepare repository for CI/CD                      | ART-16_Sys-Team_24.4.12 |
+      | ASX-2 - Implement stage deployment                        | ART-16_Sys-Team_24.4.12 |
+      | ASX-3 - Prepare L&P deployment                            | ART-16_Sys-Team_24.4.13 |
+      | ASX-4 - Implement prod deployment                         | ART-16_Sys-Team_24.4.13 |
+      | ASX-5 - Setup monitoring dashboard                        | ART-16_Sys-Team_25.1.1  |
+      | ASX-6 - Establish a solution wide holistic testing vision | ART-16_E2E-Test_24.4.1  |
+      | ASX-7 - Prepare an E2E Smoke Test in CI                   |                         |
+
+  Scenario: Error Messages for tickets where no team sprint exists
+
+  Scenario: Error Messages for tickets where no team sprint exists

data/features/cache_boards.feature

@@ -0,0 +1,24 @@
+Feature: Cache boards
+  In order to quickly manipulate sprints in a Jira instance having hundreds of boards
+  As a user
+  I need the boards I am interested in to be cached
+
+  Background:
+    Given the following environment variables are set:
+      | name                  | value    |
+      | JIRA_BOARD_NAME_REGEX | Delivery |
+    And I successfully run `jira-auto-tool --board-list`
+
+  Scenario: After being found the boards are no longer searched for
+    When I successfully run `jira-auto-tool --jira-http-debug --board-list`
+    Then the output contains no requests that enumerate the list of boards
+
+  Scenario: The cache is invalidated after one hour
+    Given I wait for over a day
+    When I successfully run `jira-auto-tool --jira-http-debug --board-list`
+    Then the output contains requests that enumerate the list of boards
+
+  Scenario: Explicitly clear the cache
+    When I successfully run `jira-auto-tool --jira-http-debug --board-cache-clear --board-list`
+    Then the output contains requests that enumerate the list of boards
+

data/features/control_http_request_rate_limit.feature

@@ -0,0 +1,17 @@
+Feature: Control the HTTP request rate limit
+  In order to work against a JIRA instance imposing API rate limits
+  As a user
+  I need the ability to control the HTTP request limit
+
+  Scenario Outline: Limiting the request rate
+    Given the following environment variables are set:
+      | name                         | value           |
+      | JAT_RATE_LIMIT_IN_SECONDS    | <rate_limit>    |
+      | JAT_RATE_INTERVAL_IN_SECONDS | <rate_interval> |
+    Then successfully running `jira-auto-tool --board-list --sprint-prefix` takes between <minimal_time> and <maximal_time> seconds
+
+    Examples:
+      | rate_limit | rate_interval | minimal_time | maximal_time |
+      | 0          | 0             | 0            | 5            |
+      | 1          | 2             | 1            | 20           |
+      | 1          | 10            | 18           | 120          |

data/features/create_sprints_using_existing_ones_as_reference.feature

@@ -0,0 +1,79 @@
+Feature: Add sprints using existing ones as reference
+  In order to prepare for multi-team sprints in the future
+  As an RTE
+  I need the ability to add sprints according to sprint/team prefixes
+
+  Background:
+    Given a Jira Scrum board
+    And the board only has the following sprints:
+      | comment                 | name                   | length | start_date              | state  |
+      | none added since closed | Food_Supply_25.1.3     | 2-week | 2025-02-01 11:00:00 UTC | closed |
+      | "sprints                | Food_Delivery_25.1.4   | 4-day  | 2025-02-01 11:00:00 UTC | future |
+      | expected to be          | Food_Market_25.2.1     | 3-week | 2025-02-01 11:00:00 UTC | active |
+      | added"                  | Food_Restaurant_25.2.1 | 4-week | 2025-02-21 11:00:00 UTC | future |
+
+  Scenario: Add several sprints using existing sprint prefixes
+    When I successfully run `jira-auto-tool --sprint-add=25.3.1,4`
+    Then afterwards the board only has the following sprints:
+      | name                   | start_date              | state  |
+      | Food_Supply_25.1.3     | 2025-02-01 11:00:00 UTC | closed |
+      | Food_Delivery_25.1.4   | 2025-02-01 11:00:00 UTC | future |
+      | Food_Delivery_25.3.1   | 2025-02-05 11:00:00 UTC | future |
+      | Food_Delivery_25.3.2   | 2025-02-09 11:00:00 UTC | future |
+      | Food_Delivery_25.3.3   | 2025-02-13 11:00:00 UTC | future |
+      | Food_Delivery_25.3.4   | 2025-02-17 11:00:00 UTC | future |
+      | Food_Market_25.2.1     | 2025-02-01 11:00:00 UTC | active |
+      | Food_Market_25.3.1     | 2025-02-22 11:00:00 UTC | future |
+      | Food_Market_25.3.2     | 2025-03-15 11:00:00 UTC | future |
+      | Food_Market_25.3.3     | 2025-04-05 11:00:00 UTC | future |
+      | Food_Market_25.3.4     | 2025-04-26 11:00:00 UTC | future |
+      | Food_Restaurant_25.2.1 | 2025-02-21 11:00:00 UTC | future |
+      | Food_Restaurant_25.3.1 | 2025-03-21 11:00:00 UTC | future |
+      | Food_Restaurant_25.3.2 | 2025-04-18 11:00:00 UTC | future |
+      | Food_Restaurant_25.3.3 | 2025-05-16 11:00:00 UTC | future |
+      | Food_Restaurant_25.3.4 | 2025-06-13 11:00:00 UTC | future |
+
+  Scenario: Add several planning interval sprints
+    When I successfully run `jira-auto-tool --sprint-add=25.2.2,3  --sprint-add=25.3.1,4  --sprint-add=25.4.1,5`
+    Then afterwards the board only has the following sprints:
+      | name                   | start_date              | state  |
+      | Food_Supply_25.1.3     | 2025-02-01 11:00:00 UTC | closed |
+      | Food_Delivery_25.1.4   | 2025-02-01 11:00:00 UTC | future |
+      | Food_Delivery_25.2.2   | 2025-02-05 11:00:00 UTC | future |
+      | Food_Delivery_25.2.3   | 2025-02-09 11:00:00 UTC | future |
+      | Food_Delivery_25.2.4   | 2025-02-13 11:00:00 UTC | future |
+      | Food_Delivery_25.3.1   | 2025-02-17 11:00:00 UTC | future |
+      | Food_Delivery_25.3.2   | 2025-02-21 11:00:00 UTC | future |
+      | Food_Delivery_25.3.3   | 2025-02-25 11:00:00 UTC | future |
+      | Food_Delivery_25.3.4   | 2025-03-01 11:00:00 UTC | future |
+      | Food_Delivery_25.4.1   | 2025-03-05 11:00:00 UTC | future |
+      | Food_Delivery_25.4.2   | 2025-03-09 11:00:00 UTC | future |
+      | Food_Delivery_25.4.3   | 2025-03-13 11:00:00 UTC | future |
+      | Food_Delivery_25.4.4   | 2025-03-17 11:00:00 UTC | future |
+      | Food_Delivery_25.4.5   | 2025-03-21 11:00:00 UTC | future |
+      | Food_Market_25.2.1     | 2025-02-01 11:00:00 UTC | active |
+      | Food_Market_25.2.2     | 2025-02-22 11:00:00 UTC | future |
+      | Food_Market_25.2.3     | 2025-03-15 11:00:00 UTC | future |
+      | Food_Market_25.2.4     | 2025-04-05 11:00:00 UTC | future |
+      | Food_Market_25.3.1     | 2025-04-26 11:00:00 UTC | future |
+      | Food_Market_25.3.2     | 2025-05-17 11:00:00 UTC | future |
+      | Food_Market_25.3.3     | 2025-06-07 11:00:00 UTC | future |
+      | Food_Market_25.3.4     | 2025-06-28 11:00:00 UTC | future |
+      | Food_Market_25.4.1     | 2025-07-19 11:00:00 UTC | future |
+      | Food_Market_25.4.2     | 2025-08-09 11:00:00 UTC | future |
+      | Food_Market_25.4.3     | 2025-08-30 11:00:00 UTC | future |
+      | Food_Market_25.4.4     | 2025-09-20 11:00:00 UTC | future |
+      | Food_Market_25.4.5     | 2025-10-11 11:00:00 UTC | future |
+      | Food_Restaurant_25.2.1 | 2025-02-21 11:00:00 UTC | future |
+      | Food_Restaurant_25.2.2 | 2025-03-21 11:00:00 UTC | future |
+      | Food_Restaurant_25.2.3 | 2025-04-18 11:00:00 UTC | future |
+      | Food_Restaurant_25.2.4 | 2025-05-16 11:00:00 UTC | future |
+      | Food_Restaurant_25.3.1 | 2025-06-13 11:00:00 UTC | future |
+      | Food_Restaurant_25.3.2 | 2025-07-11 11:00:00 UTC | future |
+      | Food_Restaurant_25.3.3 | 2025-08-08 11:00:00 UTC | future |
+      | Food_Restaurant_25.3.4 | 2025-09-05 11:00:00 UTC | future |
+      | Food_Restaurant_25.4.1 | 2025-10-03 11:00:00 UTC | future |
+      | Food_Restaurant_25.4.2 | 2025-10-31 11:00:00 UTC | future |
+      | Food_Restaurant_25.4.3 | 2025-11-28 11:00:00 UTC | future |
+      | Food_Restaurant_25.4.4 | 2025-12-26 11:00:00 UTC | future |
+      | Food_Restaurant_25.4.5 | 2026-01-23 11:00:00 UTC | future |

data/features/list_boards.feature

@@ -0,0 +1,12 @@
+Feature: List Boards
+  # TODO: add Supply and Delivery boards so they are listed and checked
+  Scenario: List Boards
+    When I successfully run `jira-auto-tool --board-list`
+    Then the output should match:
+    """
+    \+------------------------------+----\+
+    \|\s+Boards\s+\|
+    \+----+-\+-----+-\+-------------+----\+
+    \| Project Key\s+\| Name \s+\| Board UI URL\s+\|
+    \+----+-\+-----+-\+-------------+----\+
+    """

data/features/list_project_fields.feature

@@ -0,0 +1,89 @@
+Feature: List Project Ticket Fields
+  In order to understand the project ticket expectations
+  As a Jira user
+  I need to list the project ticket fields
+
+  Scenario: List Project Ticket Fields
+    Given a Jira project
+    When I successfully run `jira-auto-tool --project-field-list`
+    Then the output should contain:
+      """
+      +-------------+-------------------+---------------------+------------+---------------------------------------------------------------------------------------------------------------------+
+      | Ticket Type | Field Key         | Field Name          | Field Type | Allowed Values                                                                                                      |
+      +-------------+-------------------+---------------------+------------+---------------------------------------------------------------------------------------------------------------------+
+      | Bug         | assignee          | Assignee            | user       | n/a                                                                                                                 |
+      | Bug         | attachment        | Attachment          | array      | n/a                                                                                                                 |
+      | Bug         | components        | Components          | array      | []                                                                                                                  |
+      | Bug         | customfield_10001 | Team                | team       | n/a                                                                                                                 |
+      | Bug         | customfield_10020 | Sprint              | array      | n/a                                                                                                                 |
+      | Bug         | customfield_10081 | Expected Start      | date       | n/a                                                                                                                 |
+      | Bug         | customfield_10082 | Implementation Team | option     | ["A16 CRM (10044)", "A16 E2E-Test (10045)", "A16 Logistic (10048)", "A16 Platform (10046)", "A16 Sys-Team (10047)"] |
+      | Bug         | description       | Description         | string     | n/a                                                                                                                 |
+      """
+    Then the output should contain:
+      """
+      | Epic        | assignee          | Assignee            | user       | n/a                                                                                                                 |
+      | Epic        | attachment        | Attachment          | array      | n/a                                                                                                                 |
+      | Epic        | components        | Components          | array      | []                                                                                                                  |
+      | Epic        | customfield_10001 | Team                | team       | n/a                                                                                                                 |
+      | Epic        | customfield_10020 | Sprint              | array      | n/a                                                                                                                 |
+      | Epic        | customfield_10081 | Expected Start      | date       | n/a                                                                                                                 |
+      | Epic        | customfield_10082 | Implementation Team | option     | ["A16 CRM (10044)", "A16 E2E-Test (10045)", "A16 Logistic (10048)", "A16 Platform (10046)", "A16 Sys-Team (10047)"] |
+      | Epic        | description       | Description         | string     | n/a                                                                                                                 |
+      | Epic        | fixVersions       | Fix versions        | array      | []                                                                                                                  |
+      | Epic        | issuelinks        | Linked Issues       | array      | n/a                                                                                                                 |
+      | Epic        | issuetype         | Issue Type          | issuetype  | ["Epic (10000)"]                                                                                                    |
+      | Epic        | labels            | Labels              | array      | n/a                                                                                                                 |
+      | Epic        | priority          | Priority            | priority   | ["Highest (1)", "High (2)", "Medium (3)", "Low (4)", "Lowest (5)"]                                                  |
+      """
+    Then the output should contain:
+      """
+      | Story       | assignee          | Assignee            | user       | n/a                                                                                                                 |
+      | Story       | attachment        | Attachment          | array      | n/a                                                                                                                 |
+      | Story       | components        | Components          | array      | []                                                                                                                  |
+      | Story       | customfield_10001 | Team                | team       | n/a                                                                                                                 |
+      | Story       | customfield_10020 | Sprint              | array      | n/a                                                                                                                 |
+      | Story       | customfield_10081 | Expected Start      | date       | n/a                                                                                                                 |
+      | Story       | customfield_10082 | Implementation Team | option     | ["A16 CRM (10044)", "A16 E2E-Test (10045)", "A16 Logistic (10048)", "A16 Platform (10046)", "A16 Sys-Team (10047)"] |
+      | Story       | description       | Description         | string     | n/a                                                                                                                 |
+      | Story       | fixVersions       | Fix versions        | array      | []                                                                                                                  |
+      | Story       | issuelinks        | Linked Issues       | array      | n/a                                                                                                                 |
+      | Story       | issuetype         | Issue Type          | issuetype  | ["Story (10003)"]                                                                                                   |
+      | Story       | labels            | Labels              | array      | n/a                                                                                                                 |
+      | Story       | parent            | Parent              | issuelink  | n/a                                                                                                                 |
+      | Story       | priority          | Priority            | priority   | ["Highest (1)", "High (2)", "Medium (3)", "Low (4)", "Lowest (5)"]                                                  |
+      """
+    Then the output should contain:
+      """
+      | Sub-task    | assignee          | Assignee            | user       | n/a                                                                                                                 |
+      | Sub-task    | attachment        | Attachment          | array      | n/a                                                                                                                 |
+      | Sub-task    | components        | Components          | array      | []                                                                                                                  |
+      | Sub-task    | customfield_10001 | Team                | team       | n/a                                                                                                                 |
+      | Sub-task    | customfield_10020 | Sprint              | array      | n/a                                                                                                                 |
+      | Sub-task    | customfield_10081 | Expected Start      | date       | n/a                                                                                                                 |
+      | Sub-task    | customfield_10082 | Implementation Team | option     | ["A16 CRM (10044)", "A16 E2E-Test (10045)", "A16 Logistic (10048)", "A16 Platform (10046)", "A16 Sys-Team (10047)"] |
+      | Sub-task    | description       | Description         | string     | n/a                                                                                                                 |
+      | Sub-task    | fixVersions       | Fix versions        | array      | []                                                                                                                  |
+      | Sub-task    | issuelinks        | Linked Issues       | array      | n/a                                                                                                                 |
+      | Sub-task    | issuetype         | Issue Type          | issuetype  | ["Sub-task (10006)"]                                                                                                |
+      | Sub-task    | labels            | Labels              | array      | n/a                                                                                                                 |
+      | Sub-task    | parent            | Parent              | issuelink  | n/a                                                                                                                 |
+      | Sub-task    | priority          | Priority            | priority   | ["Highest (1)", "High (2)", "Medium (3)", "Low (4)", "Lowest (5)"]                                                  |
+      """
+    Then the output should contain:
+      """
+      | Task        | assignee          | Assignee            | user       | n/a                                                                                                                 |
+      | Task        | attachment        | Attachment          | array      | n/a                                                                                                                 |
+      | Task        | components        | Components          | array      | []                                                                                                                  |
+      | Task        | customfield_10001 | Team                | team       | n/a                                                                                                                 |
+      | Task        | customfield_10020 | Sprint              | array      | n/a                                                                                                                 |
+      | Task        | customfield_10081 | Expected Start      | date       | n/a                                                                                                                 |
+      | Task        | customfield_10082 | Implementation Team | option     | ["A16 CRM (10044)", "A16 E2E-Test (10045)", "A16 Logistic (10048)", "A16 Platform (10046)", "A16 Sys-Team (10047)"] |
+      | Task        | description       | Description         | string     | n/a                                                                                                                 |
+      | Task        | fixVersions       | Fix versions        | array      | []                                                                                                                  |
+      | Task        | issuelinks        | Linked Issues       | array      | n/a                                                                                                                 |
+      | Task        | issuetype         | Issue Type          | issuetype  | ["Task (10005)"]                                                                                                    |
+      | Task        | labels            | Labels              | array      | n/a                                                                                                                 |
+      | Task        | parent            | Parent              | issuelink  | n/a                                                                                                                 |
+      | Task        | priority          | Priority            | priority   | ["Highest (1)", "High (2)", "Medium (3)", "Low (4)", "Lowest (5)"]                                                  |
+      """