Jira

Het fijne aan de software is dat je een prima overzicht hebt van de taken die er aan jouw profiel hangen. Je kunt hierdoor makkelijk prioriteiten stellen. Daarnaast is het fijn dat je met meerdere tegelijkertijd in een project kunt werken en altijd de laatste bestanden kunt gebruiken zodat iedereen altijd met hetzelfde bestand kan werken.

Het dashboard op de homepage komt wel wat rommelig over. Je moet goed kijken wat er in welke kolom staat.

Jira is an immensely powerful issue management tool. It's JQL language provides ultimate flexibility to satisfy the needs of all roles on a product/project team. It's easy to use (if agile concepts are familiar to you and semi-intuitive if they're not), easy to deploy (especially if you're using Jira Cloud) and easy to integrate with.

The pricing model for add-ons. You could have a 100 users registered to your Jira instance, have an add-on that is used by a small handful of power users, and still be paying a license fee for all 100 users. Very annoying!

Jira has a weekly release schedule which means the product is always being improved or changed. This is usually a good thing, although I will admit that sometimes it isn't. Jira is also incredibly functional for a broad range of use cases, from managing a simple to-do list, team task tracking, process automation, to software development. They do a good job of making it user friendly and easy to onboard, especially since they started making drastic UI improvements a little over a year ago.

A consequence of being capable of so much is that it can be hard to configure initially. More specifically, which features you need and which can be disabled. There are a lot of great features but some just complicate the workflow, and it usually takes time to figure this out.

JIRA is an industry standard tool, due to this it's very well known and a colloquial metaphor for "tickets" in and of itself. JIRA is able to handle monolithic projects and the many related projects with regard to them.
JIRA is very good at allowing and automatically building self-referencing tickets within it's comments and ticket parts, if you put a ticket title into a ticket it will automatically reference the actual ticket with a link. It is also very good at adding to existing tickets with related tasks, sub-tasks, and prioritization. JIRA also is considered in almost every third party tool with a massive volume of software that offers "JIRA plugins" considering it's high stature with the IT community.

JIRA is "the tool" but it's not "a good tool" for every project and company size. JIRA is like other commercial grade products that just aren't designed for simple day to day use. While it opens up nicely and begins to make tons of sense in larger projects, larger organizations, and larger teams it often doesn't show the same beauty with simple projects and day to day ticket tracking.

Additionally, the JQL language is ridiculous follows in the foot steps of many other proprietary languages that are only great for constant users of JIRA. While that's the implied scenario because as mentioned JIRA is "the tool" it's not always the case. When my day is split 20 ways, I have little time to sit down and do more than plug in a JIRA ticket number to get to the issue to investigate, review, get sign off on a fix, and apply.

JIRA is also having what appears to be a lot of difficulties this year staying online with their new data center providers. I don't remember ever having these issues prior to their most recent move.