Jira Anti-Patterns

Alienating your Jira admin

Scrum Master Does All The Issue Updates

Not updating your issues at least once/day

Overly sophisticated and restrictive workflows

Workflows with no waiting statuses

No distinction between the backlog and planned work

Implementing unnecessary approvals

Configuring Kanban or Scrum boards with Assignee based swim lanes

Using Jira as the primary conduit for communication

Burying required information in comments

Notification barrage

Categorizing with versions, epics, and/or sprints

  • DevOps
  • Support
  • Tech Debt

Tracking time unnecessarily

Trying to create the ultimate configuration on Day 1

Assuming Jira will solve process, structure, or cultural issues

Using Jira as Big Brother

Blanket rollout of plug-ins

Backlog hoarders

One size fits all approach

Orphaned objects

Having Jira driven by people who don’t use it

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store