Can bug in TFS be integrated with defects in HP ALM in a two-way manner? If yes, how will it work?
Its very much feasible. Either you can go with existing solutions available in market. Or you can build your own with the help of APIs provided by both of the systems. Both systems are very rich in terms of communication interfaces.
https://admhelp.microfocus.com/alm/en/12.55/api_refs/REST_TECH_PREVIEW/ALM_REST_API_TP.html
https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-4.1
https://learn.microsoft.com/en-us/azure/devops/integrate/concepts/dotnet-client-libraries?view=vsts
You can work with this and figureout your way. Else there are very good tools available to do this.
Related
Does anybody know how to use ROS/ROS2 for the multi-agent system? I know there are other software for multi agent, but I heard that ROS is suitable for this. Does anybody know the specific ideas?
ROS is a middleware framework for creating a distributed system of nodes based on the publish/subscribe methodology. It can certainly be used for a multi-agent system. You should read through the ros wiki. It has a lot of great info and is a very easy way to start learning the ideas.
we're currently working on a BDI framework for ROS2 targeting Multi Agent Systems (MAS), thus facilitating its development. Repository is here and user's documentation here. The plans are dynamically computed via a PDDL 2.1 based planning system (which is PlanSys2). It's still under development, so there can be bugs here and there. We're currently try to solve them and then the idea is to lean toward a more flexible reasoning behaviour, while keeping in consideration real time constraints and/or computational feasibility of the plan execution.
If that might fulfill your needs, give it a look and share your feedback!
I am looking for project planing support in JIRA. An upcoming project contains different work streams which can be quite independent of each other. For each work stream the corresponded tickets will be stored in JIRA.
Assuming that for each ticket the effort estimation in days is derived. I am looking for the following visualization:
WS1: Ticket_1_1 Ticket_1_2 Ticket_1_3 ...
WS2: Ticket_2_1 Ticket_2_2 Ticket_2_3 ...
....
WSN: Ticket_N_1 Ticket_N_2 Ticket_N_3 ...
Accompanied by the calendar time axis.
The representation will be used for the definition of implementation order and challenging of project timelines (or ticket descoping)
Does JIRA support such or similar visualizations (may be through plugins)?
Could you please provide some suitable ideas?
Best,
you may try Portfolio for Jira.
Example: https://www.teamlead.ru/pages/viewpage.action?pageId=18514705
HTH
JIRA is available for rich visualization and reporting functions as it widely uses in the industry. JIRA dashboards and visual boards make better sense in the data-driven approaches. This may help you to have a better discussion on JIRA reportings HERE.
Let me recommend some sort of tools you may be helped in this context. ZOHO , ASANA
I am doing research for Kanban tools which has the ability to download Work items from TFS, what i have found so far are Eylean board and UrbanTurtle. If you could post others, I would really appreciate this, but the requirements is a solid supported tools, not open source rarely updated projects.
Yes, SwiftKanban from Digite integrates with TFS. You can check it out at http://www.swiftkanban.com. It supports not only TFS but a large number of other software engineering and related tools. All the best!
LeanKit is a solid Kanban tool, arguably one of the leaders in Kanban tools along with Swift Digite. LeanKit does have functionality that allows it to integrate with TFS.
http://www.leankit.com
From Telerik, TeamPulse has an excellent TFS integration story and has some Kanban features, most notably the WIP limits on columns. It is more of a Scrumban implementation but it could meet your needs.
http://www.telerik.com/agile-project-management-tools/
Cheers.
What functionality are you looking for exactly? TFS 2013 (and TFS Online) have a Kanban board
http://msdn.microsoft.com/en-us/library/jj838789.aspx
There is some support in TFS 2012 (Post Update 1), but not sure how much they have.
I currently work in a company that uses FogBugz for issue and bug tracking and SourceGear Vault for source control.
We are now introducing Team Foundation Server. Clearly TFS will replace Vault for source control. My question is, with the following requirements:
Large existing base of FogBugz cases (some obviously open) that we need to support ongoing
Support desk needs to be able to raise bugs / support calls
Want changes to source to be linked to a case number
... what is the best split between using FogBugz cases and TFS WorkItems?
Is it possible to totally migrate from FogBugz to TFS?
If it is not possible to migrate from FogBugz to TFS then what is the best way to use the FogBugz case and TFS workitems together?
Initially I'd say bugs and defects stay in FogBugz, stuff on the project plan as work items. You could manually get the developers to create a work item for each case in FogBugz and associate the code with that work item but I can hear the howls of derision already :-)
You might want to take a look at the TFS Integration platform. I don't know if there are any tools that link directly to FogBugz but these tools are highly extensible. You could then decide to either migrate everything in to TFS or run both systems and synchronise. Running both is nice as each discipline can use the tool they are most familiar with, devs use TFS for everything and the testers / support can continue to use Fogbugz and the toolkit keeps everything in step.
What are some of the models/methods (best practices) to promote code between environments? What kind of models do you use?
What are some of the models/methods (best practices) to promote code between environments?
A good place to start looking is looking at the Microsoft Team Foundation Server Branching Guidance: Code Promotion Best Practices. This version is for 2008 but will get you started in understanding approaches.
From there, take a look at the Visual Studio TFS Branching Guide 2010. Download the TFS_Branching_Guide_2010_Complete_Package. Inside you will find a variety of diagrams/documents that will assist you in deciding how to best approach code promotion.
What kind of models do you use?
Our company model varies from project to project due to the complexity and release model. In all cases though we have separate branches for each release/hotfix and a main branch which acts as the pulse of our application "A build that should never fail." From there though we use a variety of approaches- some using a Review WI before promotion, others a bit more free in the promotion process. All that to say, based on your scenario and goals you will find your approach adjusting to fit those needs.