The default check-in action for a work-item is "resolve". I'd like to set it to "associate" so that this work item isn't automaticaly closed if I check-in stuff too fast. How can I do that?
Yup, the check-in action can only be associated to a state transition (i.e. Active to Resolved). In my blog post that Fredrick linked to (http://www.woodwardweb.com/vsts/top_tfs_tip_3_r.html) I talk about how to remove that. You'll need to customize the work item for everyone in your team project to make this happen. For help on that see
http://msdn.microsoft.com/en-us/library/ms243849(VS.80).aspx
Martin Woodward blogged about how to remove the "Resolve" action from the check-in dialog as a work-around for this:
http://www.woodwardweb.com/vsts/top_tfs_tip_3_r.html
For newer versions of Visual Studio, you can now set this default in the UI:
Tools -> Options -> Source Control -> Visual Studio Team Foundation Server -> (Uncheck) Resolve associated work items on check-in
Unlike previous versions, in VS2015 the registry key solution seems to work in the cases we need!
I just went to
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0\TeamFoundation\SourceControl\Behavior
and changed ResolveAsDefaultCheckinAction from True to False.
Related
I know I can manually go to PR and uncheck Viewed. Is there a shortcut to uncheck on all files in the PR?
Found some relevant issues on GitHub
https://github.com/refined-github/refined-github/issues/2444
Why I want to do it?
To be able to see the comments and expand the cards which are collapsed because I manually marked viewed.
I tried Option+Click on Mac , didn't work for me.
Don't think the UI currently supports that. It looks like you need to tick, all checkboxes manually. Or come up with a JavaScript to find and click them for you.
Try that in your browser console.
document.getElementsByName("viewed").forEach(ch => {if(ch.checked) {ch.click()}})
I have been tasked with figuring out to solve this issue. I am working on a project that uses TFVC in Azure Devops and when a check-in is made the system adds that comment to the discussion thread on the work item. What setting can I change to turn that off?
UPDATED:
I created a test TFVC project in a separate DevOps account that I had with no extensions installed. Checked in changes, a link was added to the Development sections as expected but just like described above it was also added to the discussion, see screenshot. So this appears to be default behavior so how do we turn it off?
As far as I know, you cannot turn this feature off once you have linked the checkin with the work item.
Does TFVC in Azure DevOps automatically write the check-in comment to
the discussion for a work item?
For this issue, the answer is no. The comment added in Check in will be used as the title of the changeset(TFVC) and will not be automatically written to the discussion of the work item.
Changesets will be linked to the Development field of the work item to drive development.
Does TFVC in Azure DevOps automatically write the check-in comment to the discussion for a work item?
Obviously not.
Automatically write check-in comments to the discussion of work items is not applicable to all users, so MS does not add it as the default behavior.
And as test, I could not found this issue on my side, and you could also to check this issue on the other organization or new organization.
As a bold guess, your organization may have one extension installed and these behaviors are performed by this extension, like Work Item Autosave. But I could not sure it, you need to check your extensions one by one, Organization Settings->Extensions.
If you find that extension, you can disable or change the settings to disable this feature.
Hope this helps.
I have Eclipse Neon with TFS plugin
When I check pending change and I relate to work item
The problem is that the Check in Action by default is Resolve and not Associate
How do I change the default?
All I found online is about visual studio which didn't help me.
(Registry not worked HKEY_CURRENT_USER\Software\Microsoft\VisualStudio**11.0**\TeamFoundation\SourceControl\Behavior #ResolveAsDefaultCheckinAction = "False")
Unfortunately, this could not be achieved in team explorer everywhere(TFS Eclipse plugin) for now.
As a workaround, you could edit the Work Item Template definition for the types of work items you are using (Bug, Task, etc.). Then remove the Check-In Action from the Work Item Template (WIT). Once the WITs have been updated into your team project this will be available for all users. Now when you add a related work item, the only option available is Associate. However, this solution has some pros and cons. Below is a few to consider:
Pros
This change only has to be made the Team Project and nothing has to be done on the clients.
If your team not resolve the work item, removing this option is not a big deal.
Cons
This would need to be applied to all current Team Projects and would
need to update the Process Template for future Team Projects.
This removes the Resolve option for users, so there is no way to perform this action anymore.
More details about how to remove resolve option, please refer DaveShaw's answer in this question: How to disable auto done status for task in checkin
We have been using Domino on a large project for years without any real source-control (other-than server backups). So, I was rather pleased when I noted the latest Designer 8.5.3 has potential integration with SVN.
I was unable get SVN working just by following the original instructions for as already noted on Stackoverflow the update sites have moved. The solution posted on OpenNTF, only half worked, with Domino still croaking at GEF, Mylyn and some other missing plugins. After finding and installing them, I still do not seem to have source-control integration.
What I have now is the ability to create on-disk projects but I do not seem to have any source-control features. I was expecting to see menu items for commit, update, revert …etc – is this how it works in Domino?
I can of course create a repository to commit the on-disk project to but I was hoping for integration inside of Domino. Whilst having years of experience in programming I’m a novice with Eclipse. I assume that I’ve done something wrong with installing the plugins? it was certainly a complicated process trying track down missing plugins.
Has anyone tried this recently and succeeded? What files do I need to install, setting tweak, …etc, to ensure this works? I’m happy to install my Designer fresh and follow a list of instructions.
Also, am I understanding how the integration works? Will I get command integration within Designer or do I have to work separately with the on-disk projects? I was really hoping for this be easy to integrate into normal workflow so I can convert the team to using it (adding too many extra or complicated steps is unlikely to create a conversion).
I posted a screenshot of my installed plugins in case this is helpful.
Mercurial? As an aside, has anyone used Mercurial instead of SVN with Designer? I would rather use Hg as I’m using this for related Dojo projects and will be easier for the team to use one system. However, I will settle for SVN as any source-control is better than non.
Update: This is answer is now out-of-date. It is useful in that it should point users in the right direction but it isn't really a working answer anymore. I no-longer develop on Lotus Notes so I cannot update it to a current solution.
I managed to figure this out eventually but will post the solution, just in case anyone else has the same trouble.
The answer by Per Henrik Lausten was very helpful as it showed me the route to follow through the menus. The main problem is that I'm not used to how Eclipse works so I didn't realise you had to go to the "Team" menu and "Share Project" after creating the on-disk project. When I did this I discovered that both SVN and CVS were already available.
I found that SVN did not like the file:// protocol (perhaps a windows issue?) Since, I could not arrange for an SVN server on our network, I decided to go down the Mercurial route. This was better for us as our other projects are stored in Mercurial.
Setting-up Mercurial with Lotus Designer 8.5.3:
In Domino preference (File -> Preferences), set: Enable Eclipse Plugins in the Domino Designer section to ticked.
Also in the preferences set: Use Binary DXL for source control operations to unticked (File -> Preferences, Domino Designer -> Source Control). Without this ticked I was not getting text for my Lotusscript agents and it would be difficult to compare changes.
Go to File -> Application -> Install:
Select Search for new features to install and click Next.
Click Add Remote Location button
Add the url: http://mercurialeclipse.eclipselabs.org.codespot.com/hg.wiki/update_site/stable/ and give it a suitable name
Once you've added this, ensure it is ticked in the location list and click Finish
Design will then search for updates and give you a list. Untick "Only show latest version of a feature per update site"
Tick MercurialEclipse 1.6 from MercurialEclipse Stable Releaes. I found that the latest version does not work, however a previous Stackoverflow conversation indicates that version 1.6 does work.
Click finish and allow it to install.
You will be asked to approve various plugins and then to restart.
MercurialEclipse, should now be installed!
To start using Mercurial with a Domino Application:
Right-click the application in the Applications tab, select: Team Development -> Set Up Source Control for this Application.
Give the project a name and choose a location for the project to be stored.
Designer will then do a DXL export of the database to your chosen location. A Navigator tab will appear next to Applications.
Right-click your new disk-project in the Navigator and select: Team -> Share Project...
Select Mercurial from the Repository types and allow Designer to create the repository.
You should now have access to various Mercurial functions via the Team menu. (You need to make your first commit.
When you make changes you want to commit to source-control, you need to:
Right-click the application and choose: Team Development -> Sync with on disk project...
Go to the Navigator tab and right-click your on-disk project, selecting team.
Most of the above steps should be obvious but decided to post full details in case anyone struggled like I did with Eclipse and how to use it properly. Once I figured it out, it really was quite easy.
Keith Strickland has created a series of blog posts on using source control with DDE. They might help you:
Keith Strickland: source control in DDE part
1: http://www.keithstric.com/A55BAC/keithstric.nsf/default.xsp?documentId=B236F39DEAF6C52F85257A72001157BF
Keith Strickland: source control in DDE part
2: http://www.keithstric.com/A55BAC/keithstric.nsf/default.xsp?documentId=B5D76A6DA163DCB585257A7C004802B6
Keith Strickland: source control in DDE part
3: http://www.keithstric.com/A55BAC/keithstric.nsf/default.xsp?documentId=C2C46D278948A24985257A7D0055D25E
I have started to use Cloud9 IDE recently and have to say I really like it as an individual. I use VS 2010 at work and TFS 2010 too. This made me think about the TFS equivalent for Cloud9. GitHub is something I have always been aware of but never really used.
I have done my research and read docs etc, what I really need some clarification in though is the whole Work Item system. I know GitHub has an Issue tracking but does it have a Work Item system similar to TFS. With the main features such as assigning work items to developers?
A little explanation to just clarify would be fantastic. Thanks!
If you're looking for a way to have Issues show up like WorkItems in your task list in visual studio, I don't think there is a solution for this to date.
You can however assign developers to issues within GitHub:
Create or Edit an Issue
Click the gear next to "No one is assigned".
Select a member from your organization to assign the issue to them.