Comment 1 Steffen Pingel 2011-11-06 09:44:10 EST

I know that this is slightly inconsistent but we intentionally decided to omit the task key in the history to increase information density. Can you provide reasons why showing the key/id is important to you?

Comment 2 Frank Becker 2011-11-06 09:51:37 EST

(In reply to comment #1)
> I know that this is slightly inconsistent but we intentionally decided to omit
> the task key in the history to increase information density. Can you provide
> reasons why showing the key/id is important to you?

The main reason for this is that I name the branches in git  like bug_<taskkey> and when I continue work I want to switch to the branch and then activate the task.

In git i did not have the description and in the history i did not have the taskkey

i create http://review.mylyn.org/104 for this.

Comment 3 Frank Becker 2011-11-06 09:53:27 EST

Created attachment 206497 [details]
mylyn/context/zip

Comment 4 Steffen Pingel 2011-11-06 10:04:53 EST

I would recommend to include part of the summary in the task branch, e.g. bug#362989-show-task-id-in-history. We are in the process of automating that in EGit (see bug 309578). 

I'm -1 on the proposed change. I don't that's the right solution for the described problem.

Comment 5 Steffen Pingel 2011-11-06 10:05:47 EST

I have added this to the meeting agenda to discuss the proposal on the next call.

Comment 6 Steffen Pingel 2011-12-08 10:52:19 EST

We decided to leave the current UI in place for now. We will reconsider this issue when we do the next UI revamp of the task list and history drop down. I'll mark this as wontfix for now but we can always reopen later if we decide to show task IDs in additional places in the UI.