Artur,

I have simplified the issue creation form to show low friction. Please review this form and let me know if this acceptable:

Screenshot 2026-03-10 at 4.11.17 PM

Large organizations I have worked in (Cisco, Google, BMC Software) all use disciplined defect management that expects deterministic defect state transitions (as outlined here).

Further, for issue management, a project is treated as a set of compartments: for instance, a typical web app project has UI, backend, database, security and deployment. These areas as handled often by distinct tech leads since they require different skill sets.

Hence for the purpose of issue management, a project is divided into distinct and non-overlapping subareas called "components". A project with no issue components is analogous to a house without rooms. While a large house is invariably divided into rooms for distinct purposes: bedroom, bathroom, kitchen, laundry room etc.

Hence Sztab issue management provides for a simple case where a project has no components and all issues are placed in a common area. Or an advanced user can create components and segregate UI defects, backend defects, documentation defects.

The simplified issue creation form allows for frictionless creation and yet can be expanded to expose a more sophisticated workflow as shown below:

Screenshot 2026-03-10 at 4.11.26 PM

I hope this is acceptable.

Merged into wolsonsc and to be release as 1.10.0.