This is a condensed version of “8 steps to JIRA field greatness” available at: http://blogs.atlassian.com/2013/12/8-steps-to-jira-field-greatness/

1. 8 steps to
JIRA field greatness
This is a condensed version of “8 steps to JIRA field greatness” available at:
http://blogs.atlassian.com/2013/12/8-steps-to-jira-field-greatness/

2. ISSUE TYPES FIELDS WORKFLOWS
Hi! I’m the issue type bug.
I start out with fields like
summary and
description.
Once an engineer reviews
me, I get a new field called
resolution.
When someone checks
the change I get a new
field: verified build.
The Terms

3. The Problem: Field-itis
Why do I have to fill ALL this
out? Half of this isn’t even
relevant to me!

4. Diagnosing Field-itis
Are people not filling out all of
the needed information when
creating issues?

5. Diagnosing Field-itis
Do people not submit issues
because it s too much work?

6. Diagnosing Field-itis
Are certain fields collecting
bogus information because
end users don t understand
its value?

7. • What is the business value of this field?
• What is required of the end-user to submit this
information?
• When in the issue lifecycle do you need this
information?
STEP ONE"
The Cure
IN 8 EASY STEPS"

8. Order fields on screens
STEP TWO"
GOOD FLOW
Fields general to
specific and the
most important
fields are listed
first
POOR FLOW
Fields are
randomly placed
on the form
requiring many
context shifts

9. Fill out the field description
STEP THREE"
• Use the field’s description to educate users.
• Keep the description short.
• Use HTML as needed.

10. Respect the required option
STEP FOUR"
• Have a way for your users to say, “I don’t know.”
• Give each field a description (see step 3).

11. Remove unneeded fields
STEP FIVE"
Why do I have to fill ALL this
out? Half of this isn’t even
relevant to me!

12. Spread out data entry
STEP SIX"

13. Scope each field
STEP SEVEN"
• Use project contexts to limit where custom fields
show up.
• Forms that only have what's necessary make
everyone more efficient.

14. Automate Everything
STEP EIGHT"
• Rest API.
• Get high fidelity detail about reported issues
without burdening users.

15. Thank you!