Have you ever had your scrum master ask you, "what is going on with that story?" As somebody that has assumed virtually every role possible on an Agile team over the course of my career, I can assure you that I have heard it many times, and I'm sure you have too. Certainly there are many ways to answer this question, but in my opinion, the best way is to make it possible for your scrum master to find the answer for themselves, using the teams primary tool, JIRA. In this article, I explain how you can make your scrum master happy by configuring your developer's primary tools, Jira, GitHub, and Jenkins to play nicely together and update JIRA stories with all of the information that your scrum master wants to see. So let's get started.