jira-auto-tool 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (139) hide show
  1. checksums.yaml +7 -0
  2. data/.rspec +3 -0
  3. data/.rubocop.yml +291 -0
  4. data/CHANGELOG.md +5 -0
  5. data/CODE_OF_CONDUCT.md +132 -0
  6. data/Guardfile +105 -0
  7. data/LICENSE.txt +21 -0
  8. data/README.md +159 -0
  9. data/Rakefile +20 -0
  10. data/bin/jira-auto-tool +57 -0
  11. data/bin/jira-auto-tool.bat +2 -0
  12. data/bin/setup +8 -0
  13. data/bin/setup-dev-win.bat +3 -0
  14. data/cucumber.yml +7 -0
  15. data/features/align_sprint_time_in_dates.feature +33 -0
  16. data/features/assign_tickets_to_team_sprints.feature +73 -0
  17. data/features/cache_boards.feature +24 -0
  18. data/features/control_http_request_rate_limit.feature +17 -0
  19. data/features/create_sprints_using_existing_ones_as_reference.feature +79 -0
  20. data/features/list_boards.feature +12 -0
  21. data/features/list_project_fields.feature +89 -0
  22. data/features/list_sprint_prefixes.feature +77 -0
  23. data/features/quarterly_add_sprints_using_existing_ones_as_a_reference.feature +71 -0
  24. data/features/quarterly_create_sprints_until_specific_date.feature +75 -0
  25. data/features/quarterly_rename_sprints.feature +179 -0
  26. data/features/rename_sprints.feature +203 -0
  27. data/features/self_documented_command_line.feature +15 -0
  28. data/features/sprint_filtering.feature +111 -0
  29. data/features/step_definitions/execution_context_steps.rb +33 -0
  30. data/features/step_definitions/jira_board_steps.rb +102 -0
  31. data/features/step_definitions/jira_ticket_steps.rb +63 -0
  32. data/features/support/10.setup_cucumber.rb +10 -0
  33. data/features/support/env.rb +25 -0
  34. data/features/support/hooks.rb +25 -0
  35. data/features/support/setup_rspec.rb +14 -0
  36. data/features/support/setup_simplecov.rb +5 -0
  37. data/features/update_sprint_end_date_and_shift_following_ones.feature +52 -0
  38. data/lib/jira/auto/tool/board/cache.rb +67 -0
  39. data/lib/jira/auto/tool/board/unavailable_board.rb +36 -0
  40. data/lib/jira/auto/tool/board.rb +105 -0
  41. data/lib/jira/auto/tool/board_controller/options.rb +32 -0
  42. data/lib/jira/auto/tool/board_controller.rb +88 -0
  43. data/lib/jira/auto/tool/common_options.rb +37 -0
  44. data/lib/jira/auto/tool/config/options.rb +19 -0
  45. data/lib/jira/auto/tool/config.rb +64 -0
  46. data/lib/jira/auto/tool/fetch_custom_field_options.rb +47 -0
  47. data/lib/jira/auto/tool/field.rb +59 -0
  48. data/lib/jira/auto/tool/field_controller.rb +50 -0
  49. data/lib/jira/auto/tool/field_option.rb +35 -0
  50. data/lib/jira/auto/tool/get_createmeta_for_project.rb +24 -0
  51. data/lib/jira/auto/tool/helpers/environment_based_value.rb +96 -0
  52. data/lib/jira/auto/tool/helpers/option_parser.rb +16 -0
  53. data/lib/jira/auto/tool/helpers/overridable_time.rb +18 -0
  54. data/lib/jira/auto/tool/helpers/pagination.rb +50 -0
  55. data/lib/jira/auto/tool/jira_http_options.rb +20 -0
  56. data/lib/jira/auto/tool/next_sprint_creator.rb +60 -0
  57. data/lib/jira/auto/tool/performer/options.rb +76 -0
  58. data/lib/jira/auto/tool/performer/planning_increment_sprint_creator.rb +42 -0
  59. data/lib/jira/auto/tool/performer/prefix_sprint_updater.rb +42 -0
  60. data/lib/jira/auto/tool/performer/quarterly_sprint_renamer/next_name_generator.rb +60 -0
  61. data/lib/jira/auto/tool/performer/quarterly_sprint_renamer.rb +19 -0
  62. data/lib/jira/auto/tool/performer/sprint_end_date_updater.rb +55 -0
  63. data/lib/jira/auto/tool/performer/sprint_renamer/keep_same_name_generator.rb +19 -0
  64. data/lib/jira/auto/tool/performer/sprint_renamer/next_name_generator.rb +47 -0
  65. data/lib/jira/auto/tool/performer/sprint_renamer.rb +55 -0
  66. data/lib/jira/auto/tool/performer/sprint_time_in_dates_aligner.rb +52 -0
  67. data/lib/jira/auto/tool/project/options.rb +22 -0
  68. data/lib/jira/auto/tool/project/ticket_fields.rb +70 -0
  69. data/lib/jira/auto/tool/project.rb +40 -0
  70. data/lib/jira/auto/tool/rate_limited_jira_client.rb +50 -0
  71. data/lib/jira/auto/tool/request_builder/field_context_fetcher.rb +78 -0
  72. data/lib/jira/auto/tool/request_builder/field_option_fetcher.rb +54 -0
  73. data/lib/jira/auto/tool/request_builder/get.rb +29 -0
  74. data/lib/jira/auto/tool/request_builder/sprint_creator.rb +112 -0
  75. data/lib/jira/auto/tool/request_builder/sprint_state_updater.rb +60 -0
  76. data/lib/jira/auto/tool/request_builder.rb +89 -0
  77. data/lib/jira/auto/tool/setup_logging.rb +35 -0
  78. data/lib/jira/auto/tool/sprint/name.rb +105 -0
  79. data/lib/jira/auto/tool/sprint/prefix.rb +66 -0
  80. data/lib/jira/auto/tool/sprint.rb +183 -0
  81. data/lib/jira/auto/tool/sprint_controller/options.rb +61 -0
  82. data/lib/jira/auto/tool/sprint_controller.rb +152 -0
  83. data/lib/jira/auto/tool/sprint_state_controller.rb +58 -0
  84. data/lib/jira/auto/tool/team.rb +23 -0
  85. data/lib/jira/auto/tool/team_sprint_prefix_mapper/options.rb +27 -0
  86. data/lib/jira/auto/tool/team_sprint_prefix_mapper.rb +62 -0
  87. data/lib/jira/auto/tool/team_sprint_ticket_dispatcher.rb +76 -0
  88. data/lib/jira/auto/tool/ticket.rb +110 -0
  89. data/lib/jira/auto/tool/until_date.rb +68 -0
  90. data/lib/jira/auto/tool/version.rb +9 -0
  91. data/lib/jira/auto/tool.rb +216 -0
  92. data/sig/jira/sprint/tool.rbs +8 -0
  93. data/spec/jira/auto/tool/board/cache_spec.rb +179 -0
  94. data/spec/jira/auto/tool/board/unavailable_board_spec.rb +34 -0
  95. data/spec/jira/auto/tool/board_controller/options_spec.rb +52 -0
  96. data/spec/jira/auto/tool/board_controller_spec.rb +154 -0
  97. data/spec/jira/auto/tool/board_spec.rb +163 -0
  98. data/spec/jira/auto/tool/common_options_spec.rb +49 -0
  99. data/spec/jira/auto/tool/config_spec.rb +108 -0
  100. data/spec/jira/auto/tool/field_controller_spec.rb +121 -0
  101. data/spec/jira/auto/tool/field_option_spec.rb +42 -0
  102. data/spec/jira/auto/tool/field_spec.rb +99 -0
  103. data/spec/jira/auto/tool/helpers/environment_based_value_spec.rb +21 -0
  104. data/spec/jira/auto/tool/helpers/option_parser_spec.rb +21 -0
  105. data/spec/jira/auto/tool/helpers/overridable_time_spec.rb +43 -0
  106. data/spec/jira/auto/tool/helpers/pagination_spec.rb +72 -0
  107. data/spec/jira/auto/tool/jira_http_options_spec.rb +32 -0
  108. data/spec/jira/auto/tool/next_sprint_creator_spec.rb +85 -0
  109. data/spec/jira/auto/tool/performer/option_spec.rb +55 -0
  110. data/spec/jira/auto/tool/performer/planning_increment_sprint_creator_spec.rb +62 -0
  111. data/spec/jira/auto/tool/performer/prefix_sprint_updater_spec.rb +35 -0
  112. data/spec/jira/auto/tool/performer/quarterly_sprint_renamer/next_name_generator_spec.rb +175 -0
  113. data/spec/jira/auto/tool/performer/quarterly_sprint_renamer_spec.rb +239 -0
  114. data/spec/jira/auto/tool/performer/sprint_end_date_updater_spec.rb +90 -0
  115. data/spec/jira/auto/tool/performer/sprint_renamer/keep_same_name_generator_spec.rb +12 -0
  116. data/spec/jira/auto/tool/performer/sprint_renamer/next_name_generator_spec.rb +129 -0
  117. data/spec/jira/auto/tool/performer/sprint_renamer_spec.rb +240 -0
  118. data/spec/jira/auto/tool/performer/sprint_time_in_dates_aligner_spec.rb +132 -0
  119. data/spec/jira/auto/tool/project/ticket_fields_spec.rb +390 -0
  120. data/spec/jira/auto/tool/project_spec.rb +31 -0
  121. data/spec/jira/auto/tool/rate_limited_jira_client_spec.rb +82 -0
  122. data/spec/jira/auto/tool/request_builder/field_context_fetcher_spec.rb +54 -0
  123. data/spec/jira/auto/tool/request_builder/field_option_fetcher_spec.rb +64 -0
  124. data/spec/jira/auto/tool/request_builder/get_spec.rb +40 -0
  125. data/spec/jira/auto/tool/request_builder/sprint_creator_spec.rb +179 -0
  126. data/spec/jira/auto/tool/request_builder/sprint_state_updater_spec.rb +31 -0
  127. data/spec/jira/auto/tool/request_builder_spec.rb +73 -0
  128. data/spec/jira/auto/tool/sprint/name_spec.rb +101 -0
  129. data/spec/jira/auto/tool/sprint/prefix_spec.rb +207 -0
  130. data/spec/jira/auto/tool/sprint_controller_spec.rb +406 -0
  131. data/spec/jira/auto/tool/sprint_spec.rb +309 -0
  132. data/spec/jira/auto/tool/team_spec.rb +21 -0
  133. data/spec/jira/auto/tool/team_sprint_prefix_mapper_spec.rb +97 -0
  134. data/spec/jira/auto/tool/team_sprint_ticket_dispatcher_spec.rb +232 -0
  135. data/spec/jira/auto/tool/ticket_spec.rb +116 -0
  136. data/spec/jira/auto/tool/until_date_spec.rb +80 -0
  137. data/spec/jira/auto/tool_spec.rb +458 -0
  138. data/spec/spec_helper.rb +42 -0
  139. metadata +368 -0
data/features/list_sprint_prefixes.feature ADDED
@@ -0,0 +1,77 @@
1
+ Feature: List Sprint Prefixes
2
+ In order to confirm the next sprints are going to be created after the correct last sprints
3
+ As a user
4
+ I need the ability to list the sprint prefixes and their corresponding last sprint
5
+
6
+ Background:
7
+ Given a Jira Scrum board
8
+ And the board only has the following sprints:
9
+ | name | length | start_date | state |
10
+ | ART-16_CRM_24.4.1 | 2-week | 2024-12-01 11:00:00 UTC | closed |
11
+ | ART-16_E2E-Test_24.4.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
12
+ | ART-16_E2E-Test_24.4.2 | 4-day | 2024-12-05 11:00:00 UTC | future |
13
+ | ART-32_Platform_24.4.7 | 3-week | 2024-10-07 11:00:00 UTC | future |
14
+ | ART-32_Sys-Team_24.4.12 | 1-week | 2024-12-24 11:00:00 UTC | future |
15
+ | ART-32_Sys-Team_25.1.1 | 1-week | 2025-01-07 11:00:00 UTC | future |
16
+
17
+ Scenario: No filter applied
18
+ When I successfully run `jira-auto-tool --sprint-prefix-list-without-board-info`
19
+ Then the output should match:
20
+ """
21
+ \+-----------------+-------------------------\+
22
+ \| \s+ Sprint Prefixes With Corresponding Last Sprints\s+ \|
23
+ \+-----------------\+----------------\+------------------+\+----------------\+-------------------------\+-------------------------\+
24
+ \| Sprint Prefix \| Last Sprint Id \| Last Sprint Name\s+\| Length In Days \| Start Date \| End Date \|
25
+ \+-----------------\+----------------\+------------------+\+----------------\+-------------------------\+-------------------------\+
26
+ """
27
+ And the output should match:
28
+ """
29
+ .+-----------------.*
30
+ .+ Sprint Prefix .*
31
+ .+-----------------.*
32
+ .+ ART-16_E2E-Test .*
33
+ .+ ART-32_Platform .*
34
+ .+ ART-32_Sys-Team .*
35
+ .+-----------------.*
36
+ """
37
+ And the output should match:
38
+ """
39
+ .*----------------------+----------.*
40
+ .* Last Sprint Name \| Length In Days \| Start Date \| End Date .*
41
+ .*------------------------\+----------------\+-------------------------\+-------------------------.*
42
+ .* ART-16_E2E-Test_24.4.2 \| 4.0 \| 2024-12-05 11:00:00 UTC \| 2024-12-09 11:00:00 UTC .*
43
+ .* ART-32_Platform_24.4.7 \| 21.0 \| 2024-10-07 11:00:00 UTC \| 2024-10-28 11:00:00 UTC .*
44
+ .* ART-32_Sys-Team_25.1.1 \| 7.0 \| 2025-01-07 11:00:00 UTC \| 2025-01-14 11:00:00 UTC .*
45
+ .*------------------------\+----------------\+-------------------------\+-------------------------.*
46
+ """
47
+
48
+ Scenario: No filtering and including the corresponding board information
49
+ When I successfully run `jira-auto-tool --sprint-prefix-list`
50
+ Then the output should match:
51
+ """
52
+ \+-------------------+-----\+
53
+ \| \s+ Sprint Prefixes With Corresponding Last Sprints \s+ \|
54
+ \+-----------------\+----------------\+------------------------\+----------------\+-------------------------\+-------------------------\+-----------------------\+--------------------+--------\+-------------------\+
55
+ \| Sprint Prefix \| Last Sprint Id \| Last Sprint Name \| Length In Days \| Start Date \| End Date \| Board Name \| Board UI URL \s+ \| Board Project Key \|
56
+ \+-----------------\+----------------\+------------------------\+----------------\+-------------------------\+-------------------------\+-----------------------\+--------------------+--------\+-------------------\+
57
+ """
58
+ And the output should match:
59
+ """
60
+ .+-----------------.+
61
+ .+ Sprint Prefix .+
62
+ .+-----------------.+
63
+ .+ ART-16_E2E-Test .+
64
+ .+ ART-32_Platform .+
65
+ .+ ART-32_Sys-Team .+
66
+ .+-----------------.+
67
+ """
68
+ Then the output should match:
69
+ """
70
+ .+------------------------\+----------------\+-------------------------\+-------------------------.+
71
+ .+ Last Sprint Name \| Length In Days \| Start Date \| End Date .+
72
+ .+------------------------\+----------------\+-------------------------\+-------------------------.+
73
+ .+ ART-16_E2E-Test_24.4.2 \| 4.0 \| 2024-12-05 11:00:00 UTC \| 2024-12-09 11:00:00 UTC .+
74
+ .+ ART-32_Platform_24.4.7 \| 21.0 \| 2024-10-07 11:00:00 UTC \| 2024-10-28 11:00:00 UTC .+
75
+ .+ ART-32_Sys-Team_25.1.1 \| 7.0 \| 2025-01-07 11:00:00 UTC \| 2025-01-14 11:00:00 UTC .+
76
+ .+------------------------\+----------------\+-------------------------\+-------------------------.+
77
+ """
data/features/quarterly_add_sprints_using_existing_ones_as_a_reference.feature ADDED
@@ -0,0 +1,71 @@
1
+ Feature: Add sprints using existing ones as a reference
2
+ In order to prepare for sprints in the future
3
+ As an RTE
4
+ I need the ability to add sprints using the existing ones as a reference
5
+
6
+ Background:
7
+ Given a Jira Scrum board
8
+
9
+ Scenario: Board with no sprints
10
+ Given the board has no sprint
11
+ When I successfully run `jira-auto-tool --quarterly-sprint-add-one`
12
+ Then the output should match:
13
+ """
14
+ WARN.*No sprint added since no reference sprint was found!
15
+ """
16
+
17
+ Scenario: Board with only closed sprints
18
+ Given the board has only closed sprints
19
+ When I successfully run `jira-auto-tool --quarterly-sprint-add-one`
20
+ Then the output should match:
21
+ """
22
+ WARN.*No sprint added since no unclosed reference sprint was found!
23
+ """
24
+
25
+ Scenario Outline: The new sprint length is the same as the reference sprint
26
+ Given an unclosed <sprint_length> sprint named ART_Team_24.4.5 starting on <start_date_time>
27
+ When I successfully run `jira-auto-tool --quarterly-sprint-add-one`
28
+ Then a sprint named <expected_name> should exist
29
+ And it starts on <expected_start>
30
+ And it ends on <expected_end>
31
+ And its state is future
32
+
33
+ Examples:
34
+ | sprint_length | start_date_time | expected_name | expected_start | expected_end |
35
+ | 1-week | 2024-12-14 11:00 | ART_Team_24.4.6 | 2024-12-21 11:00 | 2024-12-28 11:00 |
36
+ | 2-week | 2024-12-14 14:00 | ART_Team_24.4.6 | 2024-12-28 14:00 | 2025-01-11 14:00 |
37
+ | 3-week | 2024-12-14 00:00 | ART_Team_25.1.1 | 2025-01-04 00:00 | 2025-01-25 00:00 |
38
+ | 4-week | 2024-12-14 08:00 | ART_Team_25.1.1 | 2025-01-11 08:00 | 2025-02-08 08:00 |
39
+
40
+ Scenario: Sprint is created for each sprint prefix
41
+ Given the board only has the following sprints:
42
+ | comment | name | length | start_date | state |
43
+ | no added sprint because closed | art_crm_24.4.6 | 2-week | 2024-12-14 11:00:00 UTC | closed |
44
+ | yes | art_e2e-test_24.4.12 | 3-week | 2024-12-14 11:00:00 UTC | future |
45
+ | yes | art_people_24.4.6 | 2-week | 2024-12-14 11:00:00 UTC | active |
46
+ | yes | art_sys-team_24.4.12 | 1-week | 2024-12-21 11:00:00 UTC | future |
47
+ When I successfully run `jira-auto-tool --quarterly-sprint-add-one`
48
+ Then afterwards the board only has the following sprints:
49
+ | name | start_date | state |
50
+ | art_crm_24.4.6 | 2024-12-14 11:00:00 UTC | closed |
51
+ | art_e2e-test_24.4.12 | 2024-12-14 11:00:00 UTC | future |
52
+ | art_e2e-test_25.1.1 | 2025-01-04 11:00:00 UTC | future |
53
+ | art_people_24.4.6 | 2024-12-14 11:00:00 UTC | active |
54
+ | art_people_24.4.7 | 2024-12-28 11:00:00 UTC | future |
55
+ | art_sys-team_24.4.12 | 2024-12-21 11:00:00 UTC | future |
56
+ | art_sys-team_24.4.13 | 2024-12-28 11:00:00 UTC | future |
57
+
58
+ Scenario: Sprint is created using the last sprint of a sprint prefix
59
+ Given the board only has the following sprints:
60
+ | comment | name | length | start_date | state |
61
+ | ignored since not last existing sprint | art_sys-team_24.4.10 | 1-week | 2024-12-01 11:00:00 UTC | future |
62
+ | ignored since not last existing sprint | art_sys-team_24.4.11 | 1-week | 2024-12-05 11:00:00 UTC | future |
63
+ | yes | art_sys-team_24.4.12 | 2-week | 2024-12-14 11:00:00 UTC | future |
64
+
65
+ When I successfully run `jira-auto-tool --qsao`
66
+ Then afterwards the board only has the following sprints:
67
+ | name | start_date | state |
68
+ | art_sys-team_24.4.10 | 2024-12-01 11:00:00 UTC | future |
69
+ | art_sys-team_24.4.11 | 2024-12-05 11:00:00 UTC | future |
70
+ | art_sys-team_24.4.12 | 2024-12-14 11:00:00 UTC | future |
71
+ | art_sys-team_24.4.13 | 2024-12-28 11:00:00 UTC | future |
data/features/quarterly_create_sprints_until_specific_date.feature ADDED
@@ -0,0 +1,75 @@
1
+ Feature: Add sprints until a specific date
2
+ In order to prepare for sprints in the future
3
+ As an RTE
4
+ I need the ability to add sprints until a specific date
5
+
6
+ Background:
7
+ Given a Jira Scrum board
8
+ And the current date time is "2024-10-15 15:00 UTC"
9
+
10
+ Scenario: Add sprints until specific date
11
+ Given the board only has the following sprints:
12
+ | comment | name | length | start_date | state |
13
+ | no added since closed | art_crm_24.4.1 | 2-week | 2024-12-01 11:00:00 UTC | closed |
14
+ | | art_e2e-test_24.4.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
15
+ | | art_people_24.4.6 | 3-week | 2024-10-07 11:00:00 UTC | active |
16
+ | no since after specified date | art_sys-team_24.4.12 | 1-week | 2024-12-24 11:00:00 UTC | future |
17
+ When I successfully run `jira-auto-tool --quarterly-sprint-add-until=2024-12-15`
18
+ Then afterwards the board only has the following sprints:
19
+ | name | start_date | state |
20
+ | art_crm_24.4.1 | 2024-12-01 11:00:00 UTC | closed |
21
+ | art_e2e-test_24.4.1 | 2024-12-01 11:00:00 UTC | future |
22
+ | art_e2e-test_24.4.2 | 2024-12-05 11:00:00 UTC | future |
23
+ | art_e2e-test_24.4.3 | 2024-12-09 11:00:00 UTC | future |
24
+ | art_e2e-test_24.4.4 | 2024-12-13 11:00:00 UTC | future |
25
+ | art_people_24.4.6 | 2024-10-07 11:00:00 UTC | active |
26
+ | art_people_24.4.7 | 2024-10-28 11:00:00 UTC | future |
27
+ | art_people_24.4.8 | 2024-11-18 11:00:00 UTC | future |
28
+ | art_people_24.4.9 | 2024-12-09 11:00:00 UTC | future |
29
+ | art_sys-team_24.4.12 | 2024-12-24 11:00:00 UTC | future |
30
+
31
+ Scenario: Add sprints until current quarter end
32
+ Given the board only has the following sprints:
33
+ | comment | name | length | start_date | state |
34
+ | none added since closed | art_crm_24.4.1 | 2-week | 2024-12-01 11:00:00 UTC | closed |
35
+ | | art_e2e-test_24.4.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
36
+ | | art_people_24.4.6 | 3-week | 2024-10-07 11:00:00 UTC | active |
37
+ | yes since finishes before midnight at the quarter end | art_sys-team_24.4.12 | 1-week | 2024-12-24 11:00:00 UTC | future |
38
+ When I successfully run `jira-auto-tool --quarterly-sprint-add-until=current_quarter`
39
+ Then afterwards the board only has the following sprints:
40
+ | name | start_date | state |
41
+ | art_crm_24.4.1 | 2024-12-01 11:00:00 UTC | closed |
42
+ | art_e2e-test_24.4.1 | 2024-12-01 11:00:00 UTC | future |
43
+ | art_e2e-test_24.4.2 | 2024-12-05 11:00:00 UTC | future |
44
+ | art_e2e-test_24.4.3 | 2024-12-09 11:00:00 UTC | future |
45
+ | art_e2e-test_24.4.4 | 2024-12-13 11:00:00 UTC | future |
46
+ | art_e2e-test_24.4.5 | 2024-12-17 11:00:00 UTC | future |
47
+ | art_e2e-test_24.4.6 | 2024-12-21 11:00:00 UTC | future |
48
+ | art_e2e-test_24.4.7 | 2024-12-25 11:00:00 UTC | future |
49
+ | art_e2e-test_24.4.8 | 2024-12-29 11:00:00 UTC | future |
50
+ | art_people_24.4.6 | 2024-10-07 11:00:00 UTC | active |
51
+ | art_people_24.4.7 | 2024-10-28 11:00:00 UTC | future |
52
+ | art_people_24.4.8 | 2024-11-18 11:00:00 UTC | future |
53
+ | art_people_24.4.9 | 2024-12-09 11:00:00 UTC | future |
54
+ | art_people_24.4.10 | 2024-12-30 11:00:00 UTC | future |
55
+ | art_sys-team_24.4.12 | 2024-12-24 11:00:00 UTC | future |
56
+ | art_sys-team_24.4.13 | 2024-12-31 11:00:00 UTC | future |
57
+
58
+ Scenario: Add sprints until the coming quarter end
59
+ Given the board only has the following sprints:
60
+ | comment | name | length | start_date | state |
61
+ | none added since closed | art_crm_24.4.1 | 2-week | 2024-12-01 11:00:00 UTC | closed |
62
+ | none added since goes over coming quarter end | art_e2e-test_25.1.9 | 4-day | 2025-03-30 11:00:00 UTC | future |
63
+ | | art_people_24.4.6 | 6-week | 2024-10-07 11:00:00 UTC | active |
64
+ When I successfully run `jira-auto-tool --qsau=coming_quarter`
65
+ Then afterwards the board only has the following sprints:
66
+ | name | start_date | state |
67
+ | art_crm_24.4.1 | 2024-12-01 11:00:00 UTC | closed |
68
+ | art_e2e-test_25.1.9 | 2025-03-30 11:00:00 UTC | future |
69
+ | art_people_24.4.6 | 2024-10-07 11:00:00 UTC | active |
70
+ | art_people_24.4.7 | 2024-11-18 11:00:00 UTC | future |
71
+ | art_people_24.4.8 | 2024-12-30 11:00:00 UTC | future |
72
+ | art_people_25.1.1 | 2025-02-10 11:00:00 UTC | future |
73
+ | art_people_25.1.2 | 2025-03-24 11:00:00 UTC | future |
74
+
75
+
data/features/quarterly_rename_sprints.feature ADDED
@@ -0,0 +1,179 @@
1
+ Feature: Rename sprints
2
+ In order to adjust the sprint names according to the convention and needs
3
+ As a team member
4
+ I need the ability to rename specific sprints and their followers
5
+
6
+ Background:
7
+ Given a Jira Scrum board
8
+
9
+ Scenario: Push a sprint to the next planning interval and rename followers
10
+ Given the board only has the following sprints:
11
+ | name | length | start_date | state |
12
+ | Food_Supply_25.1.2 | 2-week | 2024-12-01 11:00:00 UTC | closed |
13
+ | Food_Supply_25.1.3 | 2-week | 2024-12-01 11:00:00 UTC | closed |
14
+ | Food_Supply_25.1.4 | 2-week | 2024-12-01 11:00:00 UTC | closed |
15
+ | Food_Supply_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | closed |
16
+ | Food_Delivery_25.1.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
17
+ | Food_Delivery_25.1.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
18
+ | Food_Delivery_25.1.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
19
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
20
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
21
+ | Food_Delivery_25.2.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
22
+ | Food_Delivery_25.2.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
23
+ | Food_Delivery_25.2.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
24
+ | Food_Delivery_25.2.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
25
+ | Food_Restaurant_24.4.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
26
+ | Food_Restaurant_25.1.5 | 4-day | 2024-12-01 11:00:00 UTC | future |
27
+ | Food_Restaurant_25.2.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
28
+ | Food_Market_25.2.5 | 4-day | 2024-12-01 11:00:00 UTC | future |
29
+ | Food_Market_25.3.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
30
+ | Food_Market_25.3.2 | 4-day | 2024-12-01 11:00:00 UTC | future |
31
+ When I successfully run `jira-auto-tool --quarterly-sprint-rename=25.1.5,25.2.1`
32
+ Then afterwards the board only has the following sprints:
33
+ | name | start_date | state |
34
+ | Food_Supply_25.1.2 | 2024-12-01 11:00:00 UTC | closed |
35
+ | Food_Supply_25.1.3 | 2024-12-01 11:00:00 UTC | closed |
36
+ | Food_Supply_25.1.4 | 2024-12-01 11:00:00 UTC | closed |
37
+ | Food_Supply_25.1.5 | 2024-12-01 11:00:00 UTC | closed |
38
+ | Food_Delivery_25.1.2 | 2024-12-01 11:00:00 UTC | future |
39
+ | Food_Delivery_25.1.3 | 2024-12-01 11:00:00 UTC | future |
40
+ | Food_Delivery_25.1.4 | 2024-12-01 11:00:00 UTC | future |
41
+ | Food_Delivery_25.2.1 | 2024-12-01 11:00:00 UTC | future |
42
+ | Food_Delivery_25.2.2 | 2024-12-01 11:00:00 UTC | future |
43
+ | Food_Delivery_25.2.3 | 2024-12-01 11:00:00 UTC | future |
44
+ | Food_Delivery_25.2.4 | 2024-12-01 11:00:00 UTC | future |
45
+ | Food_Delivery_25.2.5 | 2024-12-01 11:00:00 UTC | future |
46
+ | Food_Delivery_25.2.6 | 2024-12-01 11:00:00 UTC | future |
47
+ | Food_Restaurant_24.4.1 | 2024-12-01 11:00:00 UTC | future |
48
+ | Food_Restaurant_25.2.1 | 2024-12-01 11:00:00 UTC | future |
49
+ | Food_Restaurant_25.2.2 | 2024-12-01 11:00:00 UTC | future |
50
+ | Food_Market_25.2.5 | 2024-12-01 11:00:00 UTC | future |
51
+ | Food_Market_25.3.1 | 2024-12-01 11:00:00 UTC | future |
52
+ | Food_Market_25.3.2 | 2024-12-01 11:00:00 UTC | future |
53
+
54
+ Scenario: Pull a sprint into the previous planning interval and rename followers
55
+ Given the board only has the following sprints:
56
+ | name | length | start_date | state |
57
+ | Food_Supply_25.1.2 | 2-week | 2024-12-01 11:00:00 UTC | closed |
58
+ | Food_Supply_25.1.3 | 2-week | 2024-12-01 11:00:00 UTC | closed |
59
+ | Food_Supply_25.1.4 | 2-week | 2024-12-01 11:00:00 UTC | closed |
60
+ | Food_Supply_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | closed |
61
+ | Food_Delivery_25.1.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
62
+ | Food_Delivery_25.1.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
63
+ | Food_Delivery_25.1.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
64
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
65
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
66
+ | Food_Delivery_25.2.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
67
+ | Food_Delivery_25.2.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
68
+ | Food_Delivery_25.2.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
69
+ | Food_Delivery_25.2.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
70
+ | Food_Restaurant_24.4.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
71
+ | Food_Restaurant_25.1.5 | 4-day | 2024-12-01 11:00:00 UTC | future |
72
+ | Food_Restaurant_25.2.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
73
+ | Food_Market_25.2.5 | 4-day | 2024-12-01 11:00:00 UTC | future |
74
+ | Food_Market_25.3.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
75
+ | Food_Market_25.3.2 | 4-day | 2024-12-01 11:00:00 UTC | future |
76
+ When I successfully run `jira-auto-tool --qsr=25.2.1,25.1.6`
77
+ Then afterwards the board only has the following sprints:
78
+ | name | start_date | state |
79
+ | Food_Supply_25.1.2 | 2024-12-01 11:00:00 UTC | closed |
80
+ | Food_Supply_25.1.3 | 2024-12-01 11:00:00 UTC | closed |
81
+ | Food_Supply_25.1.4 | 2024-12-01 11:00:00 UTC | closed |
82
+ | Food_Supply_25.1.5 | 2024-12-01 11:00:00 UTC | closed |
83
+ | Food_Delivery_25.1.2 | 2024-12-01 11:00:00 UTC | future |
84
+ | Food_Delivery_25.1.3 | 2024-12-01 11:00:00 UTC | future |
85
+ | Food_Delivery_25.1.4 | 2024-12-01 11:00:00 UTC | future |
86
+ | Food_Delivery_25.1.5 | 2024-12-01 11:00:00 UTC | future |
87
+ | Food_Delivery_25.1.6 | 2024-12-01 11:00:00 UTC | future |
88
+ | Food_Delivery_25.2.1 | 2024-12-01 11:00:00 UTC | future |
89
+ | Food_Delivery_25.2.2 | 2024-12-01 11:00:00 UTC | future |
90
+ | Food_Delivery_25.2.3 | 2024-12-01 11:00:00 UTC | future |
91
+ | Food_Delivery_25.2.4 | 2024-12-01 11:00:00 UTC | future |
92
+ | Food_Restaurant_24.4.1 | 2024-12-01 11:00:00 UTC | future |
93
+ | Food_Restaurant_25.1.5 | 2024-12-01 11:00:00 UTC | future |
94
+ | Food_Restaurant_25.1.6 | 2024-12-01 11:00:00 UTC | future |
95
+ | Food_Market_25.2.5 | 2024-12-01 11:00:00 UTC | future |
96
+ | Food_Market_25.3.1 | 2024-12-01 11:00:00 UTC | future |
97
+ | Food_Market_25.3.2 | 2024-12-01 11:00:00 UTC | future |
98
+
99
+ Scenario: Sprints beyond the planning interval of the sprint next to the first sprint to rename are left untouched
100
+ Given the board only has the following sprints:
101
+ | name | length | start_date | state |
102
+ | Food_Delivery_25.1.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
103
+ | Food_Delivery_25.1.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
104
+ | Food_Delivery_25.1.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
105
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
106
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
107
+ | Food_Delivery_25.2.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
108
+ | Food_Delivery_25.2.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
109
+ | Food_Delivery_25.2.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
110
+ | Food_Delivery_25.2.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
111
+ | Food_Delivery_25.3.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
112
+ | Food_Delivery_25.3.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
113
+ | Food_Delivery_26.1.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
114
+ When I successfully run `jira-auto-tool --quarterly-sprint-rename=25.1.5,25.2.1`
115
+ Then afterwards the board only has the following sprints:
116
+ | name | start_date | state |
117
+ | Food_Delivery_25.1.2 | 2024-12-01 11:00:00 UTC | future |
118
+ | Food_Delivery_25.1.3 | 2024-12-01 11:00:00 UTC | future |
119
+ | Food_Delivery_25.1.4 | 2024-12-01 11:00:00 UTC | future |
120
+ | Food_Delivery_25.2.1 | 2024-12-01 11:00:00 UTC | future |
121
+ | Food_Delivery_25.2.2 | 2024-12-01 11:00:00 UTC | future |
122
+ | Food_Delivery_25.2.3 | 2024-12-01 11:00:00 UTC | future |
123
+ | Food_Delivery_25.2.4 | 2024-12-01 11:00:00 UTC | future |
124
+ | Food_Delivery_25.2.5 | 2024-12-01 11:00:00 UTC | future |
125
+ | Food_Delivery_25.2.6 | 2024-12-01 11:00:00 UTC | future |
126
+ | Food_Delivery_25.3.1 | 2024-12-01 11:00:00 UTC | future |
127
+ | Food_Delivery_25.3.4 | 2024-12-01 11:00:00 UTC | future |
128
+ | Food_Delivery_26.1.1 | 2024-12-01 11:00:00 UTC | future |
129
+
130
+ Scenario: Rename a sprint forward in a planning interval
131
+ Given the board only has the following sprints:
132
+ | name | length | start_date | state |
133
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
134
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
135
+ | Food_Delivery_25.2.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
136
+ | Food_Delivery_25.2.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
137
+ | Food_Delivery_25.2.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
138
+ | Food_Delivery_25.2.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
139
+ | Food_Delivery_25.3.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
140
+ | Food_Delivery_25.3.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
141
+ | Food_Delivery_26.1.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
142
+ When I successfully run `jira-auto-tool --quarterly-sprint-rename=25.2.2,25.2.10`
143
+ Then afterwards the board only has the following sprints:
144
+ | name | start_date | state |
145
+ | Food_Delivery_25.1.5 | 2024-12-01 11:00:00 UTC | future |
146
+ | Food_Delivery_25.2.1 | 2024-12-01 11:00:00 UTC | future |
147
+ | Food_Delivery_25.2.10 | 2024-12-01 11:00:00 UTC | future |
148
+ | Food_Delivery_25.2.11 | 2024-12-01 11:00:00 UTC | future |
149
+ | Food_Delivery_25.2.12 | 2024-12-01 11:00:00 UTC | future |
150
+ | Food_Delivery_25.2.13 | 2024-12-01 11:00:00 UTC | future |
151
+ | Food_Delivery_25.3.1 | 2024-12-01 11:00:00 UTC | future |
152
+ | Food_Delivery_25.3.4 | 2024-12-01 11:00:00 UTC | future |
153
+ | Food_Delivery_26.1.1 | 2024-12-01 11:00:00 UTC | future |
154
+
155
+ Scenario: Rename a sprint backward in a planning interval
156
+ Given the board only has the following sprints:
157
+ | name | length | start_date | state |
158
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
159
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
160
+ | Food_Delivery_25.2.10 | 2-week | 2024-12-01 11:00:00 UTC | future |
161
+ | Food_Delivery_25.2.11 | 2-week | 2024-12-01 11:00:00 UTC | future |
162
+ | Food_Delivery_25.2.12 | 2-week | 2024-12-01 11:00:00 UTC | future |
163
+ | Food_Delivery_25.2.13 | 2-week | 2024-12-01 11:00:00 UTC | future |
164
+ | Food_Delivery_25.3.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
165
+ | Food_Delivery_25.3.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
166
+ | Food_Delivery_26.1.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
167
+ When I successfully run `jira-auto-tool --quarterly-sprint-rename=25.2.10,25.2.2`
168
+ Then afterwards the board only has the following sprints:
169
+ | name | start_date | state |
170
+ | Food_Delivery_25.1.5 | 2024-12-01 11:00:00 UTC | future |
171
+ | Food_Delivery_25.2.1 | 2024-12-01 11:00:00 UTC | future |
172
+ | Food_Delivery_25.2.2 | 2024-12-01 11:00:00 UTC | future |
173
+ | Food_Delivery_25.2.3 | 2024-12-01 11:00:00 UTC | future |
174
+ | Food_Delivery_25.2.4 | 2024-12-01 11:00:00 UTC | future |
175
+ | Food_Delivery_25.2.5 | 2024-12-01 11:00:00 UTC | future |
176
+ | Food_Delivery_25.3.1 | 2024-12-01 11:00:00 UTC | future |
177
+ | Food_Delivery_25.3.4 | 2024-12-01 11:00:00 UTC | future |
178
+ | Food_Delivery_26.1.1 | 2024-12-01 11:00:00 UTC | future |
179
+
data/features/rename_sprints.feature ADDED
@@ -0,0 +1,203 @@
1
+ Feature: Rename sprints
2
+ In order to adjust the sprint names according to the convention and needs
3
+ As a team member
4
+ I need the ability to rename specific sprints and their followers
5
+
6
+ Background:
7
+ Given a Jira Scrum board
8
+
9
+ Scenario: Push a sprint to the next planning interval and rename followers
10
+ Given the board only has the following sprints:
11
+ | name | length | start_date | state |
12
+ | Food_Supply_25.1.2 | 2-week | 2024-12-01 11:00:00 UTC | closed |
13
+ | Food_Supply_25.1.3 | 2-week | 2024-12-01 11:00:00 UTC | closed |
14
+ | Food_Supply_25.1.4 | 2-week | 2024-12-01 11:00:00 UTC | closed |
15
+ | Food_Supply_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | closed |
16
+ | Food_Delivery_25.1.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
17
+ | Food_Delivery_25.1.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
18
+ | Food_Delivery_25.1.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
19
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
20
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
21
+ | Food_Delivery_25.2.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
22
+ | Food_Delivery_25.2.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
23
+ | Food_Delivery_25.2.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
24
+ | Food_Delivery_25.2.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
25
+ | Food_Restaurant_24.4.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
26
+ | Food_Restaurant_25.1.5 | 4-day | 2024-12-01 11:00:00 UTC | future |
27
+ | Food_Restaurant_25.2.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
28
+ | Food_Market_25.2.5 | 4-day | 2024-12-01 11:00:00 UTC | future |
29
+ | Food_Market_25.3.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
30
+ | Food_Market_25.3.2 | 4-day | 2024-12-01 11:00:00 UTC | future |
31
+ When I successfully run `jira-auto-tool --sprint-rename=25.1.5,25.2.1`
32
+ Then afterwards the board only has the following sprints:
33
+ | name | start_date | state |
34
+ | Food_Supply_25.1.2 | 2024-12-01 11:00:00 UTC | closed |
35
+ | Food_Supply_25.1.3 | 2024-12-01 11:00:00 UTC | closed |
36
+ | Food_Supply_25.1.4 | 2024-12-01 11:00:00 UTC | closed |
37
+ | Food_Supply_25.1.5 | 2024-12-01 11:00:00 UTC | closed |
38
+ | Food_Delivery_25.1.2 | 2024-12-01 11:00:00 UTC | future |
39
+ | Food_Delivery_25.1.3 | 2024-12-01 11:00:00 UTC | future |
40
+ | Food_Delivery_25.1.4 | 2024-12-01 11:00:00 UTC | future |
41
+ | Food_Delivery_25.2.1 | 2024-12-01 11:00:00 UTC | future |
42
+ | Food_Delivery_25.2.2 | 2024-12-01 11:00:00 UTC | future |
43
+ | Food_Delivery_25.2.3 | 2024-12-01 11:00:00 UTC | future |
44
+ | Food_Delivery_25.2.4 | 2024-12-01 11:00:00 UTC | future |
45
+ | Food_Delivery_25.2.5 | 2024-12-01 11:00:00 UTC | future |
46
+ | Food_Delivery_25.2.6 | 2024-12-01 11:00:00 UTC | future |
47
+ | Food_Restaurant_24.4.1 | 2024-12-01 11:00:00 UTC | future |
48
+ | Food_Restaurant_25.2.1 | 2024-12-01 11:00:00 UTC | future |
49
+ | Food_Restaurant_25.2.2 | 2024-12-01 11:00:00 UTC | future |
50
+ | Food_Market_25.2.5 | 2024-12-01 11:00:00 UTC | future |
51
+ | Food_Market_25.3.1 | 2024-12-01 11:00:00 UTC | future |
52
+ | Food_Market_25.3.2 | 2024-12-01 11:00:00 UTC | future |
53
+
54
+ Scenario: Pull a sprint into the previous planning interval and rename followers
55
+ Given the board only has the following sprints:
56
+ | name | length | start_date | state |
57
+ | Food_Supply_25.1.2 | 2-week | 2024-12-01 11:00:00 UTC | closed |
58
+ | Food_Supply_25.1.3 | 2-week | 2024-12-01 11:00:00 UTC | closed |
59
+ | Food_Supply_25.1.4 | 2-week | 2024-12-01 11:00:00 UTC | closed |
60
+ | Food_Supply_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | closed |
61
+ | Food_Delivery_25.1.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
62
+ | Food_Delivery_25.1.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
63
+ | Food_Delivery_25.1.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
64
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
65
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
66
+ | Food_Delivery_25.2.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
67
+ | Food_Delivery_25.2.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
68
+ | Food_Delivery_25.2.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
69
+ | Food_Delivery_25.2.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
70
+ | Food_Restaurant_24.4.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
71
+ | Food_Restaurant_25.1.5 | 4-day | 2024-12-01 11:00:00 UTC | future |
72
+ | Food_Restaurant_25.2.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
73
+ | Food_Market_25.2.5 | 4-day | 2024-12-01 11:00:00 UTC | future |
74
+ | Food_Market_25.3.1 | 4-day | 2024-12-01 11:00:00 UTC | future |
75
+ | Food_Market_25.3.2 | 4-day | 2024-12-01 11:00:00 UTC | future |
76
+ When I successfully run `jira-auto-tool --sr=25.2.1,25.1.6`
77
+ Then afterwards the board only has the following sprints:
78
+ | name | start_date | state |
79
+ | Food_Supply_25.1.2 | 2024-12-01 11:00:00 UTC | closed |
80
+ | Food_Supply_25.1.3 | 2024-12-01 11:00:00 UTC | closed |
81
+ | Food_Supply_25.1.4 | 2024-12-01 11:00:00 UTC | closed |
82
+ | Food_Supply_25.1.5 | 2024-12-01 11:00:00 UTC | closed |
83
+ | Food_Delivery_25.1.2 | 2024-12-01 11:00:00 UTC | future |
84
+ | Food_Delivery_25.1.3 | 2024-12-01 11:00:00 UTC | future |
85
+ | Food_Delivery_25.1.4 | 2024-12-01 11:00:00 UTC | future |
86
+ | Food_Delivery_25.1.5 | 2024-12-01 11:00:00 UTC | future |
87
+ | Food_Delivery_25.1.6 | 2024-12-01 11:00:00 UTC | future |
88
+ | Food_Delivery_25.1.7 | 2024-12-01 11:00:00 UTC | future |
89
+ | Food_Delivery_25.1.8 | 2024-12-01 11:00:00 UTC | future |
90
+ | Food_Delivery_25.1.9 | 2024-12-01 11:00:00 UTC | future |
91
+ | Food_Delivery_25.1.10 | 2024-12-01 11:00:00 UTC | future |
92
+ | Food_Restaurant_24.4.1 | 2024-12-01 11:00:00 UTC | future |
93
+ | Food_Restaurant_25.1.5 | 2024-12-01 11:00:00 UTC | future |
94
+ | Food_Restaurant_25.1.6 | 2024-12-01 11:00:00 UTC | future |
95
+ | Food_Market_25.2.5 | 2024-12-01 11:00:00 UTC | future |
96
+ | Food_Market_25.3.1 | 2024-12-01 11:00:00 UTC | future |
97
+ | Food_Market_25.3.2 | 2024-12-01 11:00:00 UTC | future |
98
+
99
+ Scenario: Sprints beyond the planning interval of the sprint next to the first sprint to rename are also renamed
100
+ Given the board only has the following sprints:
101
+ | name | length | start_date | state |
102
+ | Food_Delivery_25.1.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
103
+ | Food_Delivery_25.1.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
104
+ | Food_Delivery_25.1.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
105
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
106
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
107
+ | Food_Delivery_25.2.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
108
+ | Food_Delivery_25.2.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
109
+ | Food_Delivery_25.2.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
110
+ | Food_Delivery_25.2.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
111
+ | Food_Delivery_25.3.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
112
+ | Food_Delivery_25.3.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
113
+ | Food_Delivery_26.1.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
114
+ When I successfully run `jira-auto-tool --sprint-rename=25.1.5,25.2.1`
115
+ Then afterwards the board only has the following sprints:
116
+ | name | start_date | state |
117
+ | Food_Delivery_25.1.2 | 2024-12-01 11:00:00 UTC | future |
118
+ | Food_Delivery_25.1.3 | 2024-12-01 11:00:00 UTC | future |
119
+ | Food_Delivery_25.1.4 | 2024-12-01 11:00:00 UTC | future |
120
+ | Food_Delivery_25.2.1 | 2024-12-01 11:00:00 UTC | future |
121
+ | Food_Delivery_25.2.2 | 2024-12-01 11:00:00 UTC | future |
122
+ | Food_Delivery_25.2.3 | 2024-12-01 11:00:00 UTC | future |
123
+ | Food_Delivery_25.2.4 | 2024-12-01 11:00:00 UTC | future |
124
+ | Food_Delivery_25.2.5 | 2024-12-01 11:00:00 UTC | future |
125
+ | Food_Delivery_25.2.6 | 2024-12-01 11:00:00 UTC | future |
126
+ | Food_Delivery_25.2.7 | 2024-12-01 11:00:00 UTC | future |
127
+ | Food_Delivery_25.2.8 | 2024-12-01 11:00:00 UTC | future |
128
+ | Food_Delivery_25.2.9 | 2024-12-01 11:00:00 UTC | future |
129
+
130
+ Scenario: Rename a sprint forward in a planning interval and all following sprints irrespective of their intervals
131
+ Given the board only has the following sprints:
132
+ | name | length | start_date | state |
133
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
134
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
135
+ | Food_Delivery_25.2.2 | 2-week | 2024-12-01 11:00:00 UTC | future |
136
+ | Food_Delivery_25.2.3 | 2-week | 2024-12-01 11:00:00 UTC | future |
137
+ | Food_Delivery_25.2.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
138
+ | Food_Delivery_25.2.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
139
+ | Food_Delivery_25.3.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
140
+ | Food_Delivery_25.3.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
141
+ | Food_Delivery_26.1.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
142
+ When I successfully run `jira-auto-tool --sprint-rename=25.2.2,25.2.10`
143
+ Then afterwards the board only has the following sprints:
144
+ | name | start_date | state |
145
+ | Food_Delivery_25.1.5 | 2024-12-01 11:00:00 UTC | future |
146
+ | Food_Delivery_25.2.1 | 2024-12-01 11:00:00 UTC | future |
147
+ | Food_Delivery_25.2.10 | 2024-12-01 11:00:00 UTC | future |
148
+ | Food_Delivery_25.2.11 | 2024-12-01 11:00:00 UTC | future |
149
+ | Food_Delivery_25.2.12 | 2024-12-01 11:00:00 UTC | future |
150
+ | Food_Delivery_25.2.13 | 2024-12-01 11:00:00 UTC | future |
151
+ | Food_Delivery_25.2.14 | 2024-12-01 11:00:00 UTC | future |
152
+ | Food_Delivery_25.2.15 | 2024-12-01 11:00:00 UTC | future |
153
+ | Food_Delivery_25.2.16 | 2024-12-01 11:00:00 UTC | future |
154
+
155
+ Scenario: Rename a sprint backward in a planning interval and all following sprints irrespective of their intervals
156
+ Given the board only has the following sprints:
157
+ | name | length | start_date | state |
158
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
159
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
160
+ | Food_Delivery_25.2.10 | 2-week | 2024-12-01 11:00:00 UTC | future |
161
+ | Food_Delivery_25.2.11 | 2-week | 2024-12-01 11:00:00 UTC | future |
162
+ | Food_Delivery_25.2.12 | 2-week | 2024-12-01 11:00:00 UTC | future |
163
+ | Food_Delivery_25.2.13 | 2-week | 2024-12-01 11:00:00 UTC | future |
164
+ | Food_Delivery_25.3.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
165
+ | Food_Delivery_25.3.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
166
+ | Food_Delivery_26.1.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
167
+ When I successfully run `jira-auto-tool --sprint-rename=25.2.10,25.2.2`
168
+ Then afterwards the board only has the following sprints:
169
+ | name | start_date | state |
170
+ | Food_Delivery_25.1.5 | 2024-12-01 11:00:00 UTC | future |
171
+ | Food_Delivery_25.2.1 | 2024-12-01 11:00:00 UTC | future |
172
+ | Food_Delivery_25.2.2 | 2024-12-01 11:00:00 UTC | future |
173
+ | Food_Delivery_25.2.3 | 2024-12-01 11:00:00 UTC | future |
174
+ | Food_Delivery_25.2.4 | 2024-12-01 11:00:00 UTC | future |
175
+ | Food_Delivery_25.2.5 | 2024-12-01 11:00:00 UTC | future |
176
+ | Food_Delivery_25.2.6 | 2024-12-01 11:00:00 UTC | future |
177
+ | Food_Delivery_25.2.7 | 2024-12-01 11:00:00 UTC | future |
178
+ | Food_Delivery_25.2.8 | 2024-12-01 11:00:00 UTC | future |
179
+
180
+ Scenario: Renaming several sprints having the same name eliminates the name duplicates
181
+ Given the board only has the following sprints:
182
+ | name | length | start_date | state |
183
+ | Food_Delivery_25.1.5 | 2-week | 2024-12-01 11:00:00 UTC | future |
184
+ | Food_Delivery_25.2.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
185
+ | Food_Delivery_25.2.10 | 2-week | 2024-12-01 11:00:00 UTC | future |
186
+ | Food_Delivery_25.2.10 | 2-week | 2024-12-01 11:00:00 UTC | future |
187
+ | Food_Delivery_25.2.10 | 2-week | 2024-12-01 11:00:00 UTC | future |
188
+ | Food_Delivery_25.2.10 | 2-week | 2024-12-01 11:00:00 UTC | future |
189
+ | Food_Delivery_25.3.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
190
+ | Food_Delivery_25.3.4 | 2-week | 2024-12-01 11:00:00 UTC | future |
191
+ | Food_Delivery_26.1.1 | 2-week | 2024-12-01 11:00:00 UTC | future |
192
+ When I successfully run `jira-auto-tool --sprint-rename=25.2.10,25.2.2`
193
+ Then afterwards the board only has the following sprints:
194
+ | name | start_date | state |
195
+ | Food_Delivery_25.1.5 | 2024-12-01 11:00:00 UTC | future |
196
+ | Food_Delivery_25.2.1 | 2024-12-01 11:00:00 UTC | future |
197
+ | Food_Delivery_25.2.2 | 2024-12-01 11:00:00 UTC | future |
198
+ | Food_Delivery_25.2.3 | 2024-12-01 11:00:00 UTC | future |
199
+ | Food_Delivery_25.2.4 | 2024-12-01 11:00:00 UTC | future |
200
+ | Food_Delivery_25.2.5 | 2024-12-01 11:00:00 UTC | future |
201
+ | Food_Delivery_25.2.6 | 2024-12-01 11:00:00 UTC | future |
202
+ | Food_Delivery_25.2.7 | 2024-12-01 11:00:00 UTC | future |
203
+ | Food_Delivery_25.2.8 | 2024-12-01 11:00:00 UTC | future |
data/features/self_documented_command_line.feature ADDED
@@ -0,0 +1,15 @@
1
+ Feature: Self Documented Command Line
2
+
3
+ Scenario Outline: The tool provides a help summary
4
+ When I run `jira-auto-tool <arguments>`
5
+ Then the output should contain:
6
+ """
7
+ Usage: jira-auto-tool [options]*
8
+
9
+ """
10
+ Examples:
11
+ | explanation | arguments |
12
+ | no argument should print the help message | |
13
+ | help flag long version | --help |
14
+ | help flag short version | -h |
15
+