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.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We use story points for most things, but for escalations we would like to keep track of the time spent on the work. We always use bugs or tasks for escalations, but not all bugs or tasks are escalations (we might include some in our sprint).
This doesn't have to be a hard requirement - prompting users to submit times would be just fine. But I would prefer not to do that to issues where it is not relevant (stories in a sprint, for example).
Is this possible?
You can add a condition in the transition. If you want it to apply only to Bugs, you would need a workflow for bugs only and your usual workflow for the other issue types. When that workflow is created, you go to the transition when you want people to enter time and you add a condition asking for time to be logged. It will be a hard requirement.
If you want more of a reminder, you can have a screen pop up when a bug is goes through a transition. To do that, you have to create a screen with the fields you want filled in and you add it to your transition. This is done by clicking "Edit" in the page of the transition and adding the screen you created in "Transition View".
Hope this helps.
I have added a transition screen also with "Log Work" as a field. "Log Work" does not show up, though I've added it to both my transition screen and the default.
"Time Tracking" does show up when included, but only the Original Estimate and the Remaining Estimate fields are shown, which is not the same as the 'Log Work' function.
Anyone have any ideas about what could be preventing the "Log Work" portion from showing up? We're using the default JIRA built-in functionality for this.