My INSURER PTE LTD - Insurtech Innovation Award 2024
Denver AUG September 2018 Jira Basics
1. JASON GOLDEN | SLALOM
PAUL STALLWORTH | CU BOULDER
Denver AUG Meeting
September 19, 2018
2.
3.
4. 4
Contegix Cloud
The ONLY partner
offering Atlassian-
specific Managed
Hosting
24x7x365
Unlimited monitoring &
support via multiple
channels
The Leader in Atlassian Managed Hosting
16+ years optimizing
Atlassian enterprise
solutions up the
application level
6. Next Meetings
Wed Oct 17, 2018
Wed Nov 14, 2018
December Social! Date TBD
And maybe two more in between!
Want to sponsor or present?
denver_co@atlassianusergroup.com
23. ATLASSIAN COMMUNITY AND AUG LEADERS
Back to (Jira) School
Jira Basics, Top Tips, and Pitfalls to Avoid
24. Be Smart With Custom Fields
This is from my production
instance! Bad Paul!
But so is this. Good Paul!
● Custom fields are displayed in the Jira UI by field ID number
○ You can get the field ID by clicking the gear icon and then hovering over Configure, the ID will be in the URL shown in
status bar
● Bob Swift’s SQL for Confluence plugin can be used to select field and field ID from Jira database and displayed on a
Confluence page - helping for creating a data dictionary of sorts for Custom Fields
29. Learn The Ways JQL and Make Filters Work For You
Modify the 'Recently Updated' quick filter's JQL from updatedDate >= -1d to updatedDate >=
startOfDay(-1). The built-in filter with -1d gets all issues updated in the last 24 hours, which means
that an issue that was being displayed 5 minutes ago can vanish from the board during office hours.
With startOfDay(-1) it would always be updated since 00:00 hours of yesterday,
Two active quick filters are applied with an implied AND, and there's no way to make them use an
OR instead. So, if you have a couple of quick filters named 'Bob' and 'John', with JQL like assignee
= bob and assignee = john, activating both quick filters at once will always show no issues in the
board. Use this tip with two different fields to supercharge your boards.
membersOf() - assignee IN membersOf(“Collaboration Squad”)
Filter on filters - filter = ‘Filter ID’ AND …
*Don’t use Filter Names, this is a performance nightmare for nested filters and can crash
your instance