We can now use gitlab issues, how are we going to use them?

[Wolthera]

On Tue, Jul 22, 2025 at 6:27 AM Emmet O'Neill <emmetoneill.pdx at gmail.com> wrote:
>
>
> Ideally I think most projects should be issues, so that we can associate them with a specific milestone.
>
> So, in my opinion, we make "Panel Cutter Tool" an issue, we populate it with a checklist of pseudo-tasks (which we can convert to proper tasks as needed for elaboration or delegation), and we associate it with a milestone like "Krita5.3".
>
> With that said, I don't necessarily have a problem with occasionally creating a milestone for big projects like you've done for the text tool. The only downside to that (that I can see) is that we can't associate it with a specific release milestone, afaik.

Yeah, I think if I were to start afresh, I'd tag my issues with 'text
tool' and then put the ones that I expect to be in the 5.3 release
inside the 5.3 milestone. The only thing I'm still unsure about is how
I'd tackle the 3 different phases: Using labels means those labels
will stay in the label dropdown long after the project is over. Using
issues to represent the phases might be overdoing it? Not sure...

>
> - Emmet


-- 
Wolthera