What do nontechnical teams, such as marketing, operations, HR, finance and legal have in common? Even though their processes might be different they can all use JIRA Core to track contracts, candidates, campaigns, approvals, and much more. But there are so many things you can tweak when setting up your team process: workflows, permissions, projects, issue types, etc. Whether you’re new to JIRA Core, or a power user, we’ll share the best practices for business teams, and give examples of how teams use JIRA Core effectively. You'll learn how to: Set up JIRA Core to match your business team's process Set up user permissions for approval processes Manage issues across different projects Handle multiple milestone due dates Expect tons of examples and aha moments when diving deep into the core of JIRA. Products covered: JIRA Core

1. (Re)Discover JIRA Core:
Tricks that make a BIG difference

5. Business teams get
started faster

7. iOS Android
What does arvo mean?

8. Legal
OperationsMarketing Finance
HR

11. Email marketing
Social mediaProduct marketing Creative
Content and PR

12. MULTIPLE DUE DATES
PROJECT SET UP
WORKING WITH OTHER TEAMS
APPROVAL PROCESSES
What we’ll be (re)discovering…
GETTING INSIGHTS
WORKING WITH YOUR TEAM

13. Project set up

14. This is Laura

16. Nikki
Creative
Matt
Content Marketing
Eloise
Head of Marketing
Jon
Social Marketing
Laura
Product Marketing Manager

17. Meet, Jordan
(The JIRA Admin)

19. Koala Uprising website project
Content
Graphics
Development
Analytics
QA LaunchTask

20. PROJECT
JIRA Core Project structure
COMPONENT
TASK
SUBTASK

21. Workflow
TO DO IN PROGRESS DONEUNDER REVIEW

22. 1 JIRA Core project
vs
Multiple JIRA Core projects

23. Koala Uprising website project
Web
Dev Task
Product marketing Content Creative
Website task Web page copy Video
Graphic 1
Graphic 2
Graphic 3
Build
QA
Launch

24. Product Marketing Content Creative Web
Koala Uprising
Project
Web copy
Blog post
Tasks
Task
Task
Task
Task
Graphic
Video
Bug
Screenshot
Design
Web task
Ad campaign
Press release
Whitepaper
Dev Task
Build
QA
Launch
Blog post
Product video

25. Multiple due dates

26. Thing to do
Thing to do
Thing to do

27. Make use of sub-tasks to
capture multiple due dates

28. Thing to doPromo Video
TO DO IN PROGRESS DONEUNDER REVIEW

32. Work with your team

33. Filter by team member

34. Filter by keyword

35. filter due date
Filter by due date

36. commenting on the go

37. Work with other teams

38. Laura needs insight into
the development
IN PROGRESS

39. Issue view
(Link an issue)
still to add

40. Adding other team
members as watchers
• Manage watchers
• Browse users permission
Permissions Required

41. Approval process

42. Transition screen

44. So managers can keep
work flowing on the go

45. User permissions

46. Working with clients or vendors
RevisionsRe: RevisionsRe: Re: RevisionsFwd: Re: Re: RevisionsRe: Fwd: Re: Re: Revisions - finalRe: Re: Re: Fwd: Re: Re: Revisions - final

47. Can browse project 2
A
Can browse, create, and
comment on project 1, 2, and 3A
B
User Groups Permission Schemes
B
Project 1 Project 2 Project 3
A A, B A
A B A
Project role Project role Project role
Global

48. XM
X
A,X
X
Can browse and
comment project
X
User Groups Permission Schemes
Global
Koala Uprising Project
External Group X
Can browse, create, and
comment on project 1, 2, and 3
Project role

49. Getting insights

51. What’s next?

52. Add-ons and integrations
and 1,200+ others

53. Takeaways•Workflow design meeting
•Insight into linking issues
•Customizing dashboards
TIPS
•Multiple due dates
•Approval
•Client view
TRICKS

54. Thank you!
SHERI • SR. PRODUCT MARKETING MANAGER
atlassian.com/jira-core
DANIEL • DESIGNER

55. Q&A