Digging for Gold - Atlassian Summit 2012
•Als KEY, PDF herunterladen•
0 gefällt mir•859 views
Empfohlen
Weitere ähnliche Inhalte
Mehr von Atlassian
Mehr von Atlassian (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Digging for Gold - Atlassian Summit 2012
- 2. Digging for Gold Using JIRA Query Language to Learn from Your Past Tony Atkins Senior Support Engineer, Atlassian
- 3. JIRA Query Language (JQL)
- 10. Change History
- 13. JQL + Change History = Change History Search
- 14. A Quick Tour
- 15. A Mountain of Data WAS WAS IN WAS NOT WAS NOT IN
- 16. Extracting the Gold • CHANGED • FROM • TO • BY • BEFORE • AFTER • DURING
- 17. “X” marks the spot... • Assignee • Reporter • Fix Version • Priority • Resolution • Status
- 18. Questions (mine)
- 19. Those who cannot remember the past are condemned to repeat it. George Santayana
- 20. Where does your backlog come from?
- 22. 53 issues
- 24. 71 issues
- 26. 13 issues
- 27. How busy are you?
- 28. 4 issues
- 30. How good are you at closing issues?
- 33. TL;DR •JQL gives you powerful searching that you can use and reuse. •The Change History shows you an issue’s past. •Change History Searching combines both to build up mountains of new data and help you mine it for gold.
- 34. Questions (yours) See me afterward!
- 35. JIRA 5 lets you mine your team’s history for pure gold. Try it today: http://bit.ly/JufP5S #summit12
- 36. Gold Pan by Nate Cull: Mine Image by “nicubunu”: http://bit.ly/HXZ6wa http://bit.ly/HXZ5ID Credits
Hinweis der Redaktion
- \n
- Hi, my name is Tony. I work for Atlassian Support. One of the key things I do in my job is try to mine data from the JIRA instance we use in support, and use that to improve our processes. I’m here to talk to you about recent improvements to JQL that are a data miner’s dream. \n\nWith JIRA 5, you can build up mountains of data and then mine it for gold, information you can use to improve the way your team works.\n
- How many of you used JIRA prior to version 4? \nHow many of you were really excited to get your hands on JQL? \nMe too.\n
- JQL added a structured language to JIRA’s search.\nYou have a full range of comparison operators like the equals, greater than, and “like” operator. You also can search for “empty” fields, which was a huge improvement.\nMost amazingly, JQL added the ability to construct highly targeted queries using the AND and OR operators.\n
- Anything you can search for, you can add to a dashboard as a table or chart.\n
- Anything you can search for, you can add to a dashboard as a table or chart.\n
- Anything you can search for, you can add to a dashboard as a table or chart.\n
- JQL lets you look at what you’re doing and pick out flakes of gold, little pieces of information you can use to understand your work and get things done better and faster. It’s like panning for gold, you set up on your stretch of the river and sift through to find as much as you can.\n
- Now you can search for issues based on their change history which takes you deep below the surface, and lets you mine for gold, extracting information about where you are now, and more importantly, how you got there.\n
- How many of you have used the change history in JIRA?\n
- How many of you use the change history in JIRA?\n\nThe change history in JIRA keeps track of every change that’s been made to an issue. It’s great for understanding the story behind a single issue.\n
- How many of you have tried this?\n
- \n
- \n
- The WAS and CHANGED operators give you a mountain of data. We’ve also added operators to help you narrow things down and really focus on the gold.\n\nThe FROM and TO operators work with the CHANGED operator to let you specify the old and new values explicitly.\n\nThe BY operator works with both the WAS and CHANGED operators, and lets you look for changes made by a specific person.\n\nThe BEFORE, AFTER and DURING operators let you narrow things down to a particular window of time.\n
- You can search all six of these fields using the change history. Between them, you can answer a bunch of questions you’ve never been able to before from within JIRA.\n
- \n
- How many of you use JIRA to keep track of your backlog? Let me show you something about your backlog using the new change history search.\n
- \n
- \n
- \n
- \n
- \n
- For those of you who aren’t math-challenged, yes, those numbers should add up, and I’ve got a ticket open to figure out why they don’t... :)\n\nJRA-28281\n
- For those of you who aren’t math-challenged, yes, those numbers should add up, and I’ve got a ticket open to figure out why they don’t... :)\n\nJRA-28281\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n