Internal ID for issue reference?

16 views

Skip to first unread message

Jorgen Bodde

unread,

Oct 29, 2016, 1:59:54 AM10/29/16

to mylifeo...@googlegroups.com

Hi,

I am in the process of figuring out how I want to divide my work for an internal project I am developing. I need some kind of system where I can divide larger parts of work (coding tasks) into smaller parts if the need arises. I do not have much time at home, so starting up with basic tasks (max one hour time) and go from there will keep momentum in my work, but also flexibility to leave the project as-is for another day when time is available. Now, I use Git for my commits and I am used to referring to an issue number. Mantis BT (a bugtracker) uses plain numbers like "00001" which I can commit on, and have reference to the issue number. Jira uses PROJECT-1 etc as issue numbers. Now, I do not want to have the issue tracker on my laptop, as my thoughts how to approach a solution can come to me at the weirdest times. Hence, MLO would be a great solution for that. However, the one thing amiss is the incremental issue number. It has to be a atomic value set either globally (I do not care if my new project does not start at 00001) or per project parent, and if inserted / selected or just available, the issue number should not change, even when new items are added before or after the item, defying the purpose of having a reference to an ID. How can I approach this? I would imagine it has multiple purposes as this "ID" can be used to refer to from sub-items in a part of a tree that does not share a common ancestor. Like, solving an issue that relates to another project's issue. Is this something MLO can provide? It would help keeping a light weight trackable list of items, without having to have a full blown issuetracker installed.