I've to create several very similar projects in TFS.
It is possible to export and import several TFS configuration, for instance, work items and process definition.
Is it possible to do the same for board configuration? For instance, column, card and tag style rules?
Try this tool Azure Boards Kanban Tools. It copies configuration between boards.
What you are looking for is export and import Board settings as Templates.
Unfortunately, there is no such build-in setting or configuration in Azure DevOps Server(TFS)/Azure DevOps Service.
You could submit a user voice. Our PM will kindly review any
suggestion.
https://developercommunity.visualstudio.com/spaces/21/visual-studio-team-services.html?type=idea
Besides, you could also try to use that extension Azure Boards Kanban Tools release by Azure DevOps Rangers. It seems come from here, take a look at this similar question: Is it possible to save Board settings as Templates in VSTS?
We have TFS 2015 (on-premise) and Microsoft Teams in the cloud.
I am trying to find the TFS plug-in (all I can see is Azure DevOps) and want to be able to show TFS information inside of Teams.
I see lots of articles on how this use to work? But can't find it in my list of plugins to add into the system.
Is there something we need to do at a server level?
Thanks
There is an official extension-- Microsoft Teams Integration.
With using this, you are able to see activity about your Azure DevOps or Team Foundation Server projects directly in your Microsoft Teams channel, for example:
Work item updates
Pull requests
Code commits
Builds
Release deployments and approvals
Work item updates
Azure DevOps Kanban board
However, as the link declare clearly, it only work with Team Foundation Server 2017 Update 2 and above. It's not able to do this with TFS2015. You need to upgrade your TFS version. With higher version, you could also get more released new features in TFS.
In our company there exist in different teams two different systems to manage the issues: Mantis and TFS. Now we have a project where a team must handle changes in both systems.
Is there a programm or a tool where tickets of TFS and Mantis can be viewed. At best there is the posibility to define relations between the tickets and prioritize them independently of the system the tickets come from.
I didn't see there is any exist tool to integrate TFS and Mantis. But there is a source control integration plugin framework for MantisBT, which supports for Github, Gitlab, Bitbucket, Gitweb, Cgit, Subversion, Mercurial, etc. You could refer to the plugin and implement TFS integration:
https://github.com/mantisbt-plugins/source-integration
Or you can use Mantis Bug Tracker REST API and TFS REST API to program your own tool.
Let me start with telling that I'm not a Microsoft Dynamics CRM specialist. I only have experience with developing .NET solutions without CRM or SharePoint and some experience how to use continues deployment of TFS to release custom applications. But for a current assignment I start with developing for Microsoft Dynamics CRM and I'm not alone.
Here we work with 2 scrum teams. Both have their own Microsoft Dynamics CRM 2016 environment and we use TFS to save our source code. Only source code, no configuration of CRM. When we release software, we need to manually merge the CRM configurations into a third environment (integration environment). This takes a lot of time and everything needs to be tested again.
I've searched on the internet and find a lot of content about customizing CRM but not how to work with multiple teams and get an automatic release pipeline for the changes both in code as in CRM.
Does anyone knows what the best practices is to develop a CRM solution with multiple teams and how to make a continues release pipeline to get the C# code and the CRM configuration automatically to the test, acceptation and production environments?
What I have done was to use the solution packager. The scrum teams would develop against their CRM instances and in a specific solutions.
They can then (either automatically using scripts and the CRM API or manually) export the solution and extract it to a version control friendly format.
This can then be committed to the version control system and then (using an automated build) get repackaged and versioned and ultimately deployed to a integration CRM instance as a managed package.
The use of managed vs un-managed packages is a bit more lengthy topic though
We have self hosted GitLab CE and Jira, we want
link git commit with jira issue
link git commit with jira issue status, like we can start/move/close issue by git issues
limit above operations on specific branches, e.g., change issue status only when commits on master branch since we perform merge request for every single feature/bug
but only GitLab EE built-in supports Jira integration, how could I do that for GitLab CE?
I'm on GitLab CE 7.8.2, Jira+Agile 6.4
I think there is now a better way:
https://docs.gitlab.com/ce/user/project/integrations/jira.html
GitLab can be configured to interact with JIRA. Configuration happens via user name and password. Connecting to a JIRA server via CAS is not possible.
Each project can be configured to connect to a different JIRA instance, see the configuration section. If you have one JIRA instance you can pre-fill the settings page with a default template. To configure the template see the Services Templates document.
Once the project is connected to JIRA, you can reference and close the issues in JIRA directly from GitLab.
You can take a look at this project : https://github.com/akraxx/gitlab-jira-integration. It's a Java application, so you will need a server with a JVM to run it.
Follow the README to know how to configure it :)
Note that, with GitLab 13.3 (August 2020), you don't have to setup a third-party integration on each project anymore.
You can do so at your managed Gitlab instance level (free edition).
Instance-level project integration management for external services
Administrators of self-managed GitLab can now integrate third-party services with all projects on the instance from a single interface.
Previously, integrations had to be configured per project, which meant that if an instance had thousands of projects, thousands of individual configurations had to be manually configured. Not only was this time-consuming, but it was also error-prone, hard to update, and made it difficult to enforce integrations as a policy.
By configuring integrations across all projects, administrators save themselves and their project owners incredible amounts of time and effort.
This is the first iteration of this functionality. In upcoming releases, we will expand this feature to the group level, add more configuration and compliance options, and more.
See Documentation and Issue.
Plus, with GitLab 13.4 (September 2020)
GitLab for Jira and DVCS Connector now in Core
For users of Jira GitLab, the GitLab for Jira app and the DVCS Connector
allow you to display information about GitLab
commits and merge requests directly in Jira.
Combined with our native
integration with Jira, you can easily move back and forth between the
two applications as you work.
These features were previously available only in our Premium plan, but
are now available to all users!
See Documentation and Issue.
See GitLab 13.6 (November 2020)
Group-level management of project integrations
In GitLab 13.3, we added the ability to enable an integration across an entire instance.
With GitLab 13.6, that feature is being expanded to allow integrations to be managed at the group level as well!
Group owners can now add an integration to a group, and that integration will be inherited by all projects under that group.
This has the potential for saving massive amounts of time, as many organizations have specific integrations that they want rolled out to every project they create.
A great example of this is using our Jira integration. If you’re using Jira, it’s almost always across the whole company. Some of these companies have thousands of projects and therefore had to configure each and every one of those integrations individually.
With group-level management of project integrations, you can add the integration at each parent group, reducing the amount of configuration required by orders of magnitude!
Read more in our announcement on the GitLab blog.
See Documentation and Epic.
With GitLab 13.10 (March 2021):
View Jira issue details in GitLab
Users of our Jira issue list feature can now view the details of an issue directly inside of GitLab! This MVC enables developers to see the details, labels, and comments on an issue, giving them the ability to stay in GitLab while working on Jira issues.
Our goal is to empower developers to stay inside of GitLab during the majority of their day, and this is now one less trip to Jira you’ll have to make.
In GitLab 13.10, this feature is available if you enable a feature flag. This feature will be enabled by default in GitLab 13.11.
See Documentation and Epic.
At the moment I think the GitLab Listener add-on for JIRA is the only way to integrate GitLab CE and JIRA. You can use commit messages to generate JIRA worklogs, comments and activities, as well as execute workflow transitions. The add-on also tries to map GitLab users to JIRA users in order to link worklogs, comments, etc. to the right user.
It's a simple add-on and maybe it does not cover all your requirements, but it's better than nothing :).