Update template for design-to-implementation tickets

[madelondohmen]

Is your feature request related to a problem? Please describe. When a design ticket is finished, a new implementation ticket is created. To create a good implementation ticket, a template must be created to determine what should and should not be included in the ticket.

Describe the solution you'd like A template that can be copy-pasted into the implementation ticket description, which can then be filled in by the design team.

[madelondohmen]

Maybe something like this will be a suiting template. Idea is to fill in as much as possible. For the UX designers, this means to fill in the "About this feature" part. The "Implementation" section will be for the developers to fill in.

---

About this feature

Detailed description

Add detailed description of the new feature you'd like to propose. If this feature is related to a problem, what problem does it solve?

Feature benefit/User story

Please also explain why this feature is important or necessary. What benefit does it bring to users? If possible, provide a user story format:

As a [type of user], I want to [action] so that [benefit].

Specifications

Please add some specifications for the implementation. What needs to be implemented to match the design?

The implementation should include…

• [ ] Specification 1
• [ ] Specification 2

Screenshots

Include screenshots of the proposed design changes here.

Figma link

Link to the Figma design for further visualization (if applicable)

Additional information

Any additional information, considerations, or context that might be helpful for understanding or evaluating the feature request.

Implementation

Possible solution

Outline your proposed solution for implementing the feature. You can include any specific ideas, designs, or functionalities here.

Alternatives considered

Describe any alternative approaches or solutions you've considered, and why you believe the proposed solution is superior.

[NoemiOverdijk]

Looks good! I have one suggestion; maybe it's a good idea to make it more explicit which parts are exlusively for the design team or the developers? To ensure people outside of the OpenKAT team know which parts to fill in when submitting a feature request.

[madelondohmen]

Maybe something like this would be better then?

---

About this feature

Detailed description

Add detailed description of the new feature you'd like to propose. If this feature is related to a problem, what problem does it solve?

Feature benefit/User story

Please also explain why this feature is important or necessary. What benefit does it bring to users? If possible, provide a user story format:

As a [type of user], I want to [action] so that [benefit].

Specifications

Please add some specifications for the implementation. What needs to be implemented to match the design?

The implementation should include…

• [ ] Specification 1
• [ ] Specification 2

Additional information

Any additional information, considerations, or context that might be helpful for understanding or evaluating the feature request.

Design

This part should only be filled in by the OpenKAT design team.

Screenshots

Include screenshots of the proposed design changes here.

Figma link

Link to the Figma design for further visualization (if applicable)

Implementation

This part should only be filled in by the developers.

Possible solution

Outline your proposed solution for implementing the feature. You can include any specific ideas, designs, or functionalities here.

Alternatives considered

Describe any alternative approaches or solutions you've considered, and why you believe the proposed solution is superior.

[madelondohmen]

Templated approved by the team.