Hello @Miłosz Jaskólski,

Please merge code to dev branch.
This is the best moment to add more information that can be helpful to prepare release notes.

• Can you prepare short overview of change that can be used in release notes?

• Please provide short GIF that showcase feature.

• If GIF make no sense, can you provide image that highlights feature that can be used in release notes (cropped & annotated)?

Task verified - QA env

@Mariusz Szymański added few changes for better UX (Polina’s comment below). Please re-review.

Suggestion:

• separate cases for “name” with empty field and ““ → to get a warning when “name” field is empty

• “description” field accepts 4096 characters → maybe worth mentioning in some sort of warning

• convert “Roadmap” issue type to “Timeline” when a request is send with older issue type name

Hello @Miłosz Jaskólski

This is the best moment to add more information that can be helpful for tester.

• What areas are affected?

• What are potential edge cases?

• Was it checked for XSS problems?

• Does change affect security, is new data exposed?

Please attach - Before / After screenshot if possible.

@Mariusz Szymański 🏓

Hello @Mariusz Szymański,
Task is ready for review.

@Miłosz Jaskólski please make sure reviewer
have easy access to contend to be reviewed.

If this is code change. Please make sure PR is created.
If this is new documentation, blogpost, etc. Please provide link to page.