This category is for making feature requests. We welcome all qualitative and constructive requests which improve Krita. We advise you to make a feature request keeping these in mind:
- Limit your request to a single feature. Great ideas can get buried within wish lists and not get the attention they deserve.
- Briefly explain the problem you currently have that you hope to solve with this request
- Explain your workflow and how it can be improved with the requested feature.
- If you have experienced this particular feature in other art programs, please describe how it would solve the situation you’re seeking to fix or improve.
- Mockups or examples will help better visualise your request.
We ask that you not include rants or emotional calls for developers. We know Krita needs to improve and welcome your input. Emotional rants or subjective opinions will leads us nowhere.
Not all requests can be answered by developers, who are limited in number and low on resources. No reply doesn’t necessarily mean your request is not acknowledged.
A high number of votes doesn’t necessarily mean that your request will be picked up by the developers. They have their own roadmap and plans. Voting helps them better gauge the interest in your request.
Please know that other users can comment on your request and question your ideas. They may agree or disagree with your proposed solution. Unless a member identifies themselves as developer and states that they are speaking on behalf of Krita project any reply made by members should considered as unofficial
It would be wise to read the official manual page about making feature request here - Developing Features — Krita Manual 5.0.0 documentation