unique id and jump-to
|
|
Our bug tracking system assigns a unique (sequential) identifier to every bug. It’s easy to use these as jump-to points or as ways of typing in dependencies. We use them extensively in discussing problems. “What are you working on?” // “1342.” // “Okay.” In most bug tracking systems you can use text like {bug:123} or just #123 to create cross references. I don’t care if the identifiers are numbers, or if they’re sequential. I just want to be able to refer to tasks by a short identifier that I didn’t have to create. I want a button or shortcut key to jump to a task by id. It would be great, too, if I could enter the id (in “find task” I guess) when creating a dependency. |
|
|
If you are on the estimates tab, and you want to see LiquidPlanner’s synthetic id, you can turn on the ID column. Go to “Actions – Advanced Actions – Customize Columns…”. As a bit of a secret (shh), if you want to jump to an item by id, you can change the location in your address from something like:
to
LiquidPlanner will then change your filters, selection, etc, and display that item selected. If you would like to enter a custom id from another system you can use the item’s “reference” field (found in the details pane under “description”). |
|
|
I’d seen the “reference” field before, but mostly I was looking for something like the task id. That column is very helpful! It would be great to have a hotkey to jump to a given task. In the meantime, this is great. Thanks! |
|
|
It would be nice to find links to task URLs in some easier way, so for instance, if someone sends a bug or something in email or we link from our wiki to a task, or I want to send a task to someone via email, I can easily copy and paste the link. |
|
|
Did you find these two commands on the actions menu? They work off the selection:
Is that what you meant? |
|
|
As long as someone else is bumping this thread… I still find the LP id numbers really anemic and depressing. We’re used to bandying about bug numbers. “Hey, would you look at my notes on #624 for me?” We just can’t, now, though. Copying a link is a 3-4 click operation, and you end up with a big link instead of a short number. If you have turned on the “id” field in the estimate view, and you double-click it to select its text, it opens the edit pane and focuses there and you can’t copy it. Once you do copy it, it doesn’t do you much good. I can’t jump to it easily, for example, so even if now I can easily say in IRC “please look at 54321” nobody can easily go right there. Everybody can probably set up LaunchBar or Quicksilver shortcuts to jump to a URL with the id jammed into it for now, I suppose, but could we get the id number exposed somewhere more accessible, like on every tab of the edit pane? Possibly “task 12345; name: ” or something. I don’t know, but it’s frustrating to be unable to use numbers. (“Look at my bug in the Foo category, it’s something about horses and rainbows in the description.”) |
|
|
Ricardo, I’ll log that as:
Actually your point about LaunchBar and Quicksilver gave me a thought. If you’re on FireFox you can add a bookmark with a keyword (lp for me) and a url like: https://app.liquidplanner.com/space/1/collabora… Now I can do “lp 1027” from the address bar, kinda handy. Anyways I’ll try to think of some easier way to expose the IDs for you, at some point I had a little prototype jump dialog that filtered the space and hopped you to ids, wonder what happened to it? |
|
|
Sure that makes sense. We have a bunch of things we want to add to the product to make it more efficient and easy to use for case management. We can look at moving the ID reference stuff up and delivering it earlier. |
|
|
In the Perl world, we would log that as “Bug: LiquidPlanner needs a Ponie” I do use Firefox… but not for LP. I find that WebKit is faster than Firefox for LP by a truly indecent amount. I use Fluid.app to make a site-specific browser to run my LiquidPlanner session. Short answer: no shortcuts. Long answer: usually, not even a URL bar. Anything to make it easy to jump to a work item by id would be welcomed by everybody here. It’s the first thing that I’m getting grief about for the push to move to LP. (Hopefully the last, too!) |


