Improve custom fields for the Development Board GitHub project

[fjbo-net]

Description

In order to transition from a bi-project development cycle into a centralized Development Board, we need to add new meaningful custom fields.

Possible Solution(s)

A clear and concise description of what you want to happen.

Objectives

Please specify what the finished feature should accomplish (one or more objectives):

• No code changes required. No feature branch required.
• [x] Add new custom field: Status
  • Field name: Status
  • Field type: Single Select
  • Options:
    • "New" (re-use existing one if available) This item hasn't been started.
    • "Blacklog" (re-use existing one if available) This item is actively being worked on
    • "Done" (re-use existing one if available) This item has been completed
• [x] Add new custom field: Priority
  • Field name: Priority
  • Field Type: Single select
  • Options:
  • Urgent (re-use existing one if available)
  • High (re-use existing one if available)
  • Medium (re-use existing one if available)
  • Low (re-use existing one if available)
• [x] Add new custom field: Size
  • Field name: Size
  • Field type: Single select
  • Options:
  • X-Large (re-use existing one if available)
  • Large (re-use existing one if available)
  • Medium (re-use existing one if available)
  • Small (re-use existing one if available)
  • Tiny (re-use existing one if available)
• [x] Add new custom field: Category
  • Field name: Category
  • Field type: Single select
  • Options:
  • Product/Project Management (re-use existing one if available)
  • Feature (re-use existing one if available)
  • Bug (re-use existing one if available)
  • Support (re-use existing one if available)
• [x] Add new custom field: Target Date
  • Field name: Target Date
  • Field type: Date
• [x] Add new custom field: Start Date
  • Field name: Start Date
  • Field type: Date
• [x] Add new custom field: Sprint
  • Field name: Sprint
  • Field type: Iteration
  • Iterations:
  • 2-week long
  • Start on closest Monday when the Cotheca Docs project was first created
  • Add past sprints up to the present day
  • Add at least the iterations a year quarter period for future (planned) sprints

Additional Context

Current custom fields for the Development Board

[fjbo-net]

Blocks:

• 27

[fjbo-net]

Blocks:

• 31

[fjbo-net]

Blocks:

• 32

[fjbo-net]

Custom field "Status" has been updated to issue objectives:

[fjbo-net]

Custom field "Priority" has been updated to fulfill issue's objectives:

[fjbo-net]

Custom field "Size" is already up to issue's objectives:

Added an understandable definition for each size:

[fjbo-net]

Custom field "Category" is up to issue's objectives:

No changes needed.

[fjbo-net]

Added new custom field "Target Date":

[fjbo-net]

Added new custom field "Start Date":

[fjbo-net]

An iteration field cannot be set to the original creation of the Cotheca Project. Reviewing the previous sprints, I have concluded that naming does not overlap. Previously, Cotheca had 24 sprints in a year, and the sprint was approximately to 2-weeks. However, it was calendar-based starting the first sprint of any given month on the 1st of the month, and the 2nd sprint starting on the 16th of the month.

Going with a new numbering system starting on next Monday (04-29-2024) will make more sense as it's a new iteration system and does not reference the previous iteration system.

The new custom field "Sprint" has been created:

Five (planned) sprints have been added to cover 2024 Q2.

[fjbo-net]

No longer a blocker for:

• 27

• 31

• 32