You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
Among several business initiative epics, we've got an Epic that corresponds to Code Quality tasks. As it's unsustainable to fully focus on that Epic for a duration of time, as well as being never-ending, it'd be nice to setup some sort of default guideline when planning a sprint.
Say, when planning a sprint, there should be a warning if there aren't at least X nr of tasks or story points from that particular epic should be included in the sprint. Is there a way to accomplish that?
Hi @Vilhelm Lundqvist -- Welcome to the Atlassian Community!
To me, this sounds like a short-term need (hopefully!) and something to handle during backlog refinement and confirmed during sprint planning...before the sprint starts.
If the team waits until after the sprint starts and then runs a check/report on missing work item types (i.e., code quality) it will appear as a scope change for the sprint.
What do you think of this approach:
It's not necessarily a short term need.
The Code Quality Epic includes a bunch off short-term need stuff like improvements to CI processes, which can be picked up and discussed as you mentioned.
But as code gets added, packages get updated, etc, needs for addressing these and performing refactors will arise as time goes on, hence the term never-ending.
I'm not necessarily looking for a warning popup when a sprint is started - moreso when creating and allocating tasks to a sprint! It can be addicting to only add feature tasks and stories to a sprint, but to maintain code health it'd be nice to get a warning during planning if there are too few Code Quality tasks.
In my experience, when refactoring and other "code smells" are addressed as part of daily working methods there is no need for separate work items to manage (or defer) such things. And it reduces "spirited conversations" of assigning story points to such types of work items.
You describe a flow to "get a warning during planning if there are too few Code Quality tasks". There is nothing built-into Jira that would support that. Perhaps there is a marketplace addon for this.
For a possible, noisy, work-around, you could try card colors and automation rules: