Hello @Michał,

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)?

@MichałFix verified- QA environment.

Hello @Michał ]

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.

@Michał approved

Hello @Kamil Zarychta,
Task is ready for review.

@Michał 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.

Since change done in

introduced new problems, I have reverted it. Instead I have increased padding for editor component (used for description field), which will make it a bit bigger. It will not take up entire space, but this is consistent with Jira and approved by @Kamil Zarychta

Hello @Krzysztof Bogdan

This is the best moment to add more description, wire-frames, comments.
Why we doing this?
What is expected result?

@Sagar Rawat Can you link it with recent description related task?