Hello!
Context
I noticed some front-end files (css, less and js mostly) have been behind our codestyle practices for a long time. E.g. usersandgroups.css. From what I understand, the way we apply codestyle rules retroactively so far is: 1. solving this ticket needs that I update an old file 2. I make sure the code I update complies to codestyle (eventually 3. I make sure the whole file is compliant to codestyle).
Problem
Personally, I rarely go to step 3 and update codestyle only where I make changes. Most of the time, updating the whole file to respect codestyle takes time and adds complexity to a solution that can far outweight the scope of the initial ticket from step 1. . In the end, those files are rarely fixed because step 2. is good only for features that are being actively worked on.
I would like to be able to keep track of such files that would badly need an update but for which the update is too heavy to add on top of the changes for another ticket. They would make for nice issues to tackle on special days in my opinion.
Proposal
I propose to introduce a new Jira label codestyle. This label would be used exclusively for tickets asssociated to the Development Issues Only component.
Conclusion
If this new label is approved, I’ll add documentation on how and when to use it in our development practices.
Thank you!
Lucas C.