Jira is a ticket tracking tool primarily used for software development. It allows users to plan, track, and manage tasks by creating tickets (issues) for each task or problem that needs to be resolved.
Conceptual Difference with Klaro Cards
- Jira is a preconfigured ticketing system
- Klaro Cards is a 100% configurable database system
What We Like About Jira
- Jira inspired our desire to escape from it forever, leading to the creation of Klaro Cards
- The humor on https://ifuckinghatejira.com/ (Klaro Cards is not behind this website)
- For ticketing or Faux-Agile development, it’s a great tool where everything is properly locked down
What We Like Less About Jira
- It’s nearly impossible to do anything other than ticketing without feeling like you're forcing a square peg into a round hole
- The interface isn't exactly pleasant, though it has improved over time
- Atlassian’s data policy is unbearable
Some Screenshots
Personal Homepage
Jira is a complex software, and you can feel it right from the homepage.
The default configuration is strongly oriented towards software development. In Jira, everything is an "Issue," with two special cases: Epic and Story.
Of course, you are allowed to change this, but to do so, you'll have to navigate the complexity of the Settings screens. Good luck.
Kanban View
Jira provides issue boards, including a Kanban board since the goal here is clearly to set up workflows. Note that the columns in the view can only be based on the issue status—no flexibility here, unlike many other tools:
Filters
Some predefined filters are available (see the right column, e.g., "My open issues"). Otherwise, you'll need to perform a search, which means learning JQL (Jira Query Language):
Issue Details
The issue details allow for writing a long description. It also includes all the defined fields and the ability to add comments:
