Community
Participate
Working Groups
It would be great, if the Gitflow integration could auto-assign feature-branches to tasks. For example, starting a feature should activate the corresponding task, finishing the feature (or checking out a different one, or switching the branch manually, ..), should deactivate it.
(In reply to Max Hohenegger from comment #0) > It would be great, if the Gitflow integration could auto-assign > feature-branches to tasks. > For example, starting a feature should activate the corresponding task, > finishing the feature (or checking out a different one, or switching the > branch manually, ..), should deactivate it. I'm not sure I would use "start a new feature" to activate a task but rather vice-versa (request this from MyLyn once this add-on is well tested). Normally in the workflow, we pull in a task, read it through and create a branch based on the task (might be a hotfix, feature or release based on the task at hand). Also, there is a small cross compatibility problem with JIRA's MyLyn integration in which the commits and the branch names are automatically populated with ticket numbers from JIRA. For example, before I updated to the new eGit git-flow add-on, my commits started with "NAME-##: " (JIRA ticket number) and my branches had "issue/NAME-XX". The recent gitFlow integration killed that (no biggie). For complete compatibility with whichever issue/bug tracking system we choose, it would be great to auto-populate the hotfix/feature/release Window with the ticket MyLyn ticket number. In Jira, that may be a story, bug or epic which, in my case, I associate with feature, hotfix and release. Everyone is different. So, I vote for auto-deactivate and request that when I start a feature/hotfix/release that it pull from the activated MyLyn/Task ticket (if available).
(In reply to David Belanger from comment #1) > I'm not sure I would use "start a new feature" to activate a task but rather > vice-versa (request this from MyLyn once this add-on is well tested). > Normally in the workflow, we pull in a task, read it through and create a > branch based on the task (might be a hotfix, feature or release based on the > task at hand). That works for me. Only, I'm not familiar with the Mylyn API, so I'm not sure if that is possible. If it is, we could probably still make it work both ways. > Also, there is a small cross compatibility problem with JIRA's MyLyn > integration in which the commits and the branch names are automatically > populated with ticket numbers from JIRA. For example, before I updated to > the new eGit git-flow add-on, my commits started with "NAME-##: " (JIRA > ticket number) and my branches had "issue/NAME-XX". The recent gitFlow > integration killed that (no biggie). Not sure if I understand, but you can change the prefixes in .git/config. There should be no problem with using "issue/" instead of "feature/". Of course this has to be configurable in the UI at some point. This is a related enhancement: https://bugs.eclipse.org/bugs/show_bug.cgi?id=309578
