Hello @Igor Hercer,

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

@Igor Hercer Fix verified- QA environment.

@Igor Hercer Adding Investigation field to JSM descriptions field causes issue that link is invalid or deleted. Also, adding this field some other types like Sub tasks also affects others issue types. Please note, the issue does not occur on Bug issue types.
https://jes-qa.warsawdynamics.com/issue/fdc289d5-a410-4948-b3a7-11f90d64ea27

@Igor Hercer Side bar jitters on selecting fields.

@Igor Hercer Issue Layout setting does not support Light theme correctly. Also, in share form selected Issue layout setting cannot be cleared if tabs are switched. Attachment added

@Igor Hercer Issue Layout setting does not support Light theme correctly. Also, in share form selected Issue layout setting cannot be cleared if tabs are switched. Attachment added

@Sagar Rawat @Parsa Shiva Ready to test

Hello @Igor Hercer ]

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.

@Igor Hercer there are still 2 thing to sort out:

1. Properly manage limitation of using global types only:
   comment in code, Jira task to improve solution, documentation for our clients.
2. Reverting unrelated JOOQ changes

@Krzysztof Bogdan Could you take a look?

@Krzysztof Bogdan 🏓

@Igor Hercer One more.
Also there are still some Michał unresolved comments.

@Krzysztof Bogdan Let’s hope that this one is the last one..

@Igor Hercer One more round 🙂

@Krzysztof Bogdan Please take a look at code review

Hello @Krzysztof Bogdan,
Task is ready for review.

@Igor Hercer 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.

Hello @Krzysztof Bogdan

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