This document discusses new features in software versions 5 and 6 of JIRA, a project management tool. It highlights improvements like increased speed, a more modern and mobile-friendly interface, and more flexible reporting. Additionally, it presents templates and blueprints as new ways to structure documents in JIRA. The rest of the document focuses on code collaboration tools and features, including distributed version control with Git, code review via pull requests, and code security with branch permissions and review/build rules. It suggests some teams may need additional integrations like hooks or add-ons to further customize their workflow.

1. The Latest and Greatest
@svenpet
http://svenpet.com
May - June 2013

2. Sven Peters
@svenpet
http://svenpet.com
Happy Ambassador

4. Apr ’12 June ’12 Aug ’12 Sep’12 Oct ’12Jan ’12 Dec ’12 Jan ’13 Feb ’13 Apr ’13
5.0 5.1 5.2 6.0
Mar ’13

5. 6
Modern. Fast. Mobile. Simple.

6. 6
Modern. Fast. Mobile. Simple.

7. JIRA 5

8. JIRA 6

10. 6
Modern. Fast. Mobile. Simple.

11. search
results
everything
editable
switch
view

12. 6
Modern. Fast. Mobile. Simple.

14. +

15. 6
Modern. Fast. Mobile. Simple.

19. 6
Modern. Fast. Mobile. Simple.
Agile

20. Plan
Epics
sprint planning

21. Work
configurable
details

22. Report
Version Report
forecast

24. Jul ’12 Aug ’12 Nov ’12 Dec ’12 Jan ’13Mar ’12 Feb ’13 Mar ’13 Apr ’13 May ’13
4.2 4.3 5.0 5.1

25. meeting notes
requirements
blog posts
file directory
release notes
marketing plans

26. gives you an empty page
and a lot of freedom

27. Templates
Our solution:

28. Templateson steroids

29. Blueprints

30. new
blueprint
new
blueprint
1. WHAT

31. placeholder text
2. HOW

32. 2. HOW

33. easy to find
3. STRUCTURE

34. sort by properties
3. STRUCTURE

35. Meeting Notes
File List

37. Meeting Notes
File List
Requirement Documents
your structured document

38. find more

40. Let's talk about coding...

41. Let's talk about...

42. Let's talk about...

43. C
D
E
T GETHER
D·V·C·S [dee] [vee] [cee] [ass]
Distributed Version Control - keeps track of software
revisions and allows many developers to work on a given
project without necessarily being connected to the
network.
The most popular DVCS software is Git.

44. C
D
E
T GETHER
D·V·C·S [dee] [vee] [cee] [ass]
Distributed Version Control - keeps track of software
revisions and allows many developers to work on a given
project without necessarily being connected to the
network.
The most popular DVCS software is Git.
Distributed

45. C
D
E
T GETHER
1000101
00101001
100010010
1001010
code
Teamsneed a central place where the
together
comes

46. Sharing code with others
Protecting your code
C
D
E
T GETHER
Your coding workflow!

47. C
D
E
T GETHER
Sharing code with others

48. learn
better
quality
feel better
blame
Why do you want to share
your code changes?

49. Discuss your code changes
they get merged!
before
use Pull Requests

50. use Pull Requests
create

51. use Pull Requests
what do
you think?
create

52. use Pull Requests
what do
you think?
invite

53. use Pull Requests
what do
you think?
discuss & approve

54. use Pull Requests
what do
you think?
merge

55. use Pull Requests
I know @Ben has
already written an
algorithm for that
involve

56. Dem Time

58. on Codeis great !
Share and Collaborate

59. on Code
should be easy and fast
Share and Collaborate

60. Simple Workflow
Pull
Request
Branch
Merge

61. Simple Workflow
Pull
Request
Branch
Merge
No Roles

62. C
D
E
T GETHER
Protecting your code

63. C
D
E
T GETHER
Make sure....

64. Pull
Request
Branch
Merge
No Roles
Simple Workflow

65. Pull
Request
Branch
Merge
No Roles
Simple Workflow

66. Pull
Request
Branch
Merge
Some Roles
Simple Workflow

67. Branch Permissions

68. Making sure
that the right people can merge code
into the right branches
#1

69. Pull
Request
Merge
minimum two approvals
Review Rules

70. Pull
Request
Merge
Review Rules

71. Making sure
that somebody reviewed the code
#2

72. Pull
Request
Merge
Build Rules

73. Pull
Request
Merge
Build Rules

74. Making sure
that the build stays green after a merge
#3

75. Project Permissions
Project
Wonderland
Project
Fairytale

76. Making sure
that the right people have access
#4
to the code they need

77. Security DevSpeed

78. The Repo Guard
Beware

79. Can I get a new Repository?
Please!

80. Can I get a new Repository?
I'll do in 3
days

81. Create Repository

82. Making sure
that the development team can move fast
#5

83. Your coding workflow!

85. Teams are different
so are their workflows

86. Some people
need more

87. Features
1.

88. Features
2

89. Feature 1:
Stash Add-ons

90. Feature 2:

91. public
class
HipChatNotifyHook
implements
AsyncPostReceiveRepositoryHook,
RepositorySettingsValidator
{
private
static
final
String
AUTH_TOKEN_KEY
=
"authToken";
private
static
final
String
ROOM_NAME_KEY
=
"roomName";
@Override
public
void
postReceive(HookContext
context,
Collection
refChanges)
{
String
room
=
context.getSettings().getString(ROOM_NAME_KEY);
createClient(context.getSettings()).notifyRoom(room,
"Stash",
HipChatTemplates.buildHtml(refChanges));
}
@Override
public
void
validate(Settings
settings,
SettingsValidationErrors
errors,
Repository
repository)
{
if
(createClient(settings).authTest())
{
errors.addFieldError(AUTH_TOKEN_KEY,
"Invalid
authorization
token");
}
}
private
HipChatProxyClient
createClient(Settings
settings)
{
return
new
HipChatProxyClient(settings.getString(AUTH_TOKEN_KEY));
}
}
Write a hook!
Unapprove reviewer hook
Protect unmerged branch hook
HipChat hook

92. Hooks
Add-Ons
or download one

93. Rock On!
svenpet.com/slides
@svenpet
http://svenpet.com