Bug 489210 - If a task is active the git checkout branch dialog shows truncated branch name instead of selected remote branch
Summary: If a task is active the git checkout branch dialog shows truncated branch nam...
Status: NEW
Alias: None
Product: EGit
Classification: Technology
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-08 08:16 EST by Andreas Höhmann CLA
Modified: 2018-03-12 06:37 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Höhmann CLA 2016-03-08 08:16:44 EST 
Steps to reproduce:
1. is select a remote branch in the git repo view to checkout them
   origin/feature/PRO-1189-Labels-Not-Updated-After-Changing-Language
2. if no task is active the the checkout as new local branch dialog shows
   source: origin/feature/PRO-1189-Labels-Not-Updated-After-Changing-Language
   branch-name: feature/PRO-1189-Labels-Not-Updated-After-Changing-Language
3. if a task (jira) is active the the checkout as new local branch dialog shows
   source: origin/feature/PRO-1189-Labels-Not-Updated-After-Changing-Language
   branch-name: issue_PRO-1189-3SU1_product_li
   the task summary is "[3SU1] product list, not all labels are updated after  changing language" 

So i guess there is maybe some interconnection here :)
Comment 1 Sam Davis CLA 2016-03-08 13:25:46 EST 
This is a feature of the EGit Mylyn integration. It is very often not the behaviour that is wanted so there should be a way to still get the default branch name when a task is active, or the feature should just be removed.
Comment 2 David Glodich CLA 2018-03-08 13:15:49 EST 
This is a very disruptive "feature"... I (and others on my team) have often unintentionally created miss-named branches after pushing changes we had intended to go into the remote branch we checked out. This causes unnecessary extra work to merge these changes back into the intended branch, and delete incorrectly named branches.

I don't understand the use case of when someone would want to have their local branch named "issue_something", instead of the same name as the branch they are checking out... Is there really one?