Suggested Guidelines for Managing Tickets in Devboard

[pwgit-create]

Suggested Guidelines for Managing Tickets in Devboard

After discovering the powerful roadmap function in our devboard, I believe it would greatly benefit us to use it
as intended. This will enhance our project management and provide a historical overview of how we've progressed.

Roadmap Overview

Guidelines for Regular Tickets and Sub-issues

---

1. Start Date: When you begin work on any ticket (e.g., creating a branch, writing documentation, or making
   inquiries), set the start date without an end date.
2. End Date: Once the ticket is completed and reviewed, the person who moves it to the "Done" column should
   set the end date.

The purpose of this practice is to take full advantage of the roadmap function, which automatically provides a
historical overview of project progress.

Please refer to the image below for an example of a sub-issue in review but without an end date. The end date will
be set once this sub-issue moves to the "Done" section.

Guidelines for Epic Tickets

---

Epic tickets are broader project assignments that benefit from being broken down into detailed sub-tasks while
maintaining a common goal in the epic ticket itself.

1. No Branch Needed: These tickets do not require a branch.
2. Review Section: They do not need to be placed in the review section.
3. Roadmap Benefits: Epic tickets are particularly useful for roadmaps since you can set start and end dates.
   The start date is when work begins on the first subtask, and the end date is an estimated future completion date
   for all sub-tasks.

• Setting an expected future date for epic tickets is not mandatory but helps with project planning.
• If all sub-issue tickets within an epic are completed before the expected end date, set the actual end date of
  the last sub-issue to reflect accurately in the roadmap.

Refer to the image below showing an epic ticket with an estimated completion date of July 20th. This date is based
on when the review for the two sub-issues is expected to be completed. If reviews are actually done by July 18th,
adjust the end date accordingly.

Implementation

I have set start and end dates on all tickets currently in the "Done" section of our devboard. Take a look at the
roadmap to see how beneficial this is for current and future projects. If there are any errors or need
corrections, please feel free to adjust the start and end dates as necessary.

Please share your thoughts on these guidelines and let me know if you think they're a good idea. Feel free to
contact me with any questions regarding their benefits or technical aspects. This is not intended to complicate
things but rather to make our project management more efficient and effective.

Thank you!

Please note in the roadmap image:

• Every entry in the roadmap is automatically added based on the start and end dates that you modify and set in
  the devboard tickets.
• The sub-issues that are completed are accurately placed in the roadmap, giving a visual overview of completed
  tickets and at which stage in the project they were made.
• Please note epic ticket Create Database #1 and Create Traverse files logic #2; both have expected end dates on the 30th of July. This date is likely to
  change as progress is made, but it helps with project planning by providing an estimated timeline for moving to
  the next stage.

[lilstiffy]

This makes total sense!
I will try to follow these guidelines to the best of my ability :)

[pwgit-create]

I'm thrilled that you sympathized with this idea! 😊

Now, I'm almost certain that this project will be a success! 🚀 No one will be penalized if they occasionally miss
following these guidelines, but if we both do our best to adhere to them, we'll have a much more enjoyable and
productive project. 🎉

You are truly a delight to work with, Stefan. I hope you know that yourself! 🤗 Let's continue making great things
happen together!