1. 1. Two types of works
    1. 1.1. 1. Checklist
    2. 1.2. 2. Projects
  2. 2. JIRA benefits
  3. 3. Hosting plans
  4. 4. Issues

Previously I was using OmniFocuse for my daily tasks management. But over the time I just realized it’s gradually losing its power, and just became yet another to-do tool packed with endless tasks which are hard to tackle down.

Since I formally started my first software developer work, and I’ve saw how the agile style workflow can actually work smoothly and deliver products, I kind of get the feel that this should be a better way of organizing my personal issues as well.

I’d like to investigate a little bit to see if it’s possible to apply JIRA for my day-to-day personal management tasks.

Two types of works

Over the time of using different tasks \ projects management tools, I kind of having identified there should be at least two types of different works, checklist and projects. One common weakness of these tools is that they can’t handle both very well.

1. Checklist

Checklist is simply a list of items, which tend to be quite easy and simple. There’s less uncertainty involved in a checklist. Once you put an item down into a checklist, it’s pretty much an actionable item by itself already, which usually can be done either in a short time period or in a straightforward means.

Checklist examples: grocery list, book list, wish list, travel list. Once you put items e.g., milk, beef or toothpaste into the grocery list, they immediately become self-explanatory and has straightforward implication of how to get them done: simply go to supermarket and grab them.

The state of an item (or issue in JIRA world) tends to transit mainly from to-do to done.

Of course, there tends to be a slightly subtler classification of two differetn flavors of checlist, which I would name as: routine list and memo list.

memo list is exaclty what discussed already, with an additoinal feature that issues are only done once. Once they are crossed-off, that’s it, they never appear again by itself. The purpose of memo list is to remind you of a bunch of things that you dont’ want to forget. To be honest, I feel this type of list can be most easily replaced by a note-taking took, e.g., Evernote, or simply write them down.

routine list would instead have repeating issues. This list intends to keep tract of a life routine that you want to practice. Such as have an issue gym workout, which recur every Monday, Wednesday. Or another issue may be revise french words which recur every two days. routine list issue also has to-do and done states, but they can go back from done to to-do again. The most usually use case for routine list is to help you repetitively practice some
skills, which may take a long-time to gradually see the benefits. This kind of list also should have a review process, to re-evalute their meaning & effectiveness every a while, just ensuring they still make sense to be there after maybe 3 years.

2. Projects

A very different type of work is projects. These are the kind of works that has a much clearer goal, and requires some explicit deliverables in a short term period. The time period can range from severald days to a few months, they are just short-term compared to routine list.

Examples can be: ‘get driving licence before end of this year’ or ‘launch my personal website’.

Compared with checklists, projects tend to be much more complicated, involving a lot of steps and brainstorming, along with much more uncertainty. This is the part where most pure to-do list tools fail to work.

Simply listing some vague steps as ‘items’ in the list doesn’t help much. Because these items can vary hugely in their job sizes and difficulties, and it’s easy to get stuck by one item.

Checklist fails also because they lack a good ability to organize time, which should be the most valuable resource for most people who need to work in the daytime while only having a few after-work hours to do their own stuffs. For them, items are better organized from a weekly perspective, which makes Agile’s sprint concept very useful.

JIRA benefits

I’ve already tried a few agile tools, e.g., JIRA, Trello and Asana, while I still feel JIRA could be a better choice.

This is because it’s the most generic tool which can suit quite a lot of different needs. Also because my company is already using it, I can gain more experience in it if I also use it in my personal time.

Hosting plans

Two hosting plans in consideration:

Plan Price Free Trial
Server $10 one time payment 30 days
Cloud $10/month for 10 users 7 days

Feel like server is the better way to go. Besides, Atlassian is selling ad-ons for its products separately, while I probably need to buy the ‘repeating issue’ add-on if I want to set-up routine lists, and this add-on is only possiblefor server-hosting.

I might start with trying the cloud-hosting for a few days, just to get familiar with the JIRA process, while at the same time installing the server hosting.


I probably still want these functionalities, but I’m not yet sure if JIRA provides, so more investigation needed…

  1. Cross-project sprint
    Through a very rough play-around, it seems you can only start sprint by selecting issues from one project. I feel like more useful if I can organize issues in separate projects, but every week I can have a global view of all the issues, and select issues I’d like to do within this week, and start a weekly sprint containing issues across different-projects. There’s an add-on Structure that seems to do something
    similar. More investigation needed.

This is possible and explained by this post: Accessing a cross-project board

  1. 1. Two types of works
    1. 1.1. 1. Checklist
    2. 1.2. 2. Projects
  2. 2. JIRA benefits
  3. 3. Hosting plans
  4. 4. Issues