As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We've recently starting using TFS. Currently just for source control.
We're considering using work items instead of our current bug tracking system. I've heard that the work flow is customizable and would like to have a go at it.
A small example is that sometimes while working a bug, someone may decide that the product documentation needs updating, maybe to explain a workaround or if the bug fix caused a change to a screen layout, new screenshots would be required in the help file. I'd like it to work so that if somebody ticks a 'required docs' check-box on the work-item, after the bug is fixed and tested, the work-item would be automatically assigned to our documentation team.
I've heard TFS does support work-flow, but am struggling to find a suitable guide on how I'd go about customizing it.
Can you point me in the right direction? Or, have I misunderstood what's possible?
Welcome to the patterns & practices Team Development with Visual Studio Team Foundation Server project site! This guide shows you how to make the most of Team Foundation Server. It starts with the end in mind, but shows you how to incrementally adopt TFS for your organization. It's a collaborative effort between patterns & practices, Team System team members, and industry experts.
http://www.codeplex.com/TFSGuide
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
As most IT companies use jira these days. Since it is a huge and complex application. But still it needs some improvements. Can someone share what improvements are needed for jira or any problem you faced while using jira?
I am asking this because in my last interview I was asked about this question, which I didnt expect, since I havent used jira so I don't know much about it. I need your help so I will be prepared in future interviews.
Atlassian tracks what users vote on at their own public JIRA instance. Here's a link to all their open JIRA issues sorted by the number of votes. Alternatively, you can read the JIRAAAARGH! chapter in my book Practical JIRA Administration.
~Matt
The list is long, and depends on what you are planning to use Jira for, such as:
who use it? (customers, developers, support, sales)
do you need svn/git support?
planning to use agile?
how do you want to open issues?
As well, while you might find many things missing, the big benefit of using Jira is that you can write your own code to achieve nearly everything.
To our needs, we found the following missing:
ability to rank issues
sending email for non Jira users
saving mail templates
24hrs issue notification
agile support (need to buy greenhoper to really support it)
front-end web forms for issue creation
You can also check Jira's new features requests and improvments
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
We had 2 projects in TFS with same code base. 2 development teams were working on those. We are now merging the code to a one project and this is not an easy task to do manually.
Before starting development in separate we have not used any functionality that TFS provides to make this sort of work easy. Like branching, labeling or any other.
Can I get some guideline or best practices to plan this kind of work so we can adopt it in future to overcome this sort of work.
Link for a TFS guide for developers will also be helpful.
Thanks in advance.
The TFS Branching Guide is probably a good place to start. It will help you with structuring your source based on different usage scenarios
You might also want to look at answers to this questions: How to branch and merge in TFS
In regards to a "TFS guide for developers" the MSDN documentation is a good starting point. Beyond that consider the various books that have been published - there are some good ones out there.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm creating a list of tools that help to log work in JIRA (apart from the worklog features provided in the JIRA interface itself).
Tools and utilities I found on the plugins.atlassian.com and googling around, are
Agile Plugin
Worklog Assistant
Hitsoft Timetracker
Universal Time Tracker
Worklog sheet
Atlassian Connectors
Tempo Plugin
JIRA Client
Talia
Does anyone know about other tools that I'm overlooking ?
Any opinion on these tools ?
Francis
I keep a list of various time tracking plugins here:
http://confluence.atlassian.com/display/JIRACOM/Using+JIRA+For+Time+Tracking
Thanks,
Christina Bang
Atlassian Sales Engineer
I've found this page while I was looking for some easy to use client tool for my ubuntu.
The orginal worklog assistant does not work well with my xmonad. (some windowing issues with java)
In the past I've written a jira-console tool in ruby but it's broken now :(
Some dependencies of soap4r not working well.
Anyway you can find it here : jira-console
Have a nice day!
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I'm currently giving a try to the new Visual Studio Scrum template and I'm looking for a the best approach and tools to enhanced product backlog management and tracking work progression. Any suggestions?
Urban Turtle (http://urbanturtle.com) is the first tool to specifically support the Microsoft Visual Studio Scrum process template (http://urbanturtle.com/blog/2010/07/08/urban-turtle-3-2-now-available/).
Let me tout my own horn for a bit, and recommend an Open Source tool I developed for my own use: Scrum Sprint Monitor (link to CodePlex). The process template you are using does not give Scrum Sprint Monitor some of the info it needs to be extra useful, but it would be very easy to add the 1 or 2 fields missing (work done and 1 other) to the process template and change the process template adapter class in the project to take advantage of them. Let me know if you are interested and I can help you through the process.
We use Rally ( http://www.rallydev.com) at our company and we're happy with it.
Prior to that we used VersionOne ( http://www.versionone.com) and it was decent.
Our company spent a good amount of time investigating and I find Rally does the job real well. Rally is hosted, which has actually turned out to be a good thing. VersionOne isn't that i'm aware of; we hosted it locally. Both provide free trials and they're willing to engage in migration efforts.
If you are using tfs you should seriously consider this:http://blogs.msdn.com/b/aaronbjork/archive/2010/05/25/announcing-team-foundation-server-scrum-v1-0-beta.aspx
This has been made in collaboration with Ken Schwaber the inventor of the Scrum. I've used actively rallydev & versionone in the past but they are too heavy, and therefore... Less agile.
The MFS template included with TFS has been adequate for our needs. We have a small group of 8 developers working on multiple projects.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
In my company we want to use Scrum lifecycle, we are using Team System 2010.
Team System is great to manage projects developpment and Scrum lifecycle.
However we are looking for a solution in order to take care of customers requirements.
A tool which give the ability to customer to send us their requests so we can plan it for next sprint.
Should i use TFS Web Access ? but which type of Work Item ?
I think TFS in general (not only Web Access) is for developpment team, not for customers ...
Any idea ?
Thanks in advance.
Take a look on UseResponse (PHP/MySQL, self-hosted). To be released in December, full sourcecode available on purchase, live demo available on USWebStyle (UseResponse authors) website.
If you're looking for something very customer oriented, what about uservoice or getsatisfaction? I also like Jira very much (best issue tracker in my opinion) but again, it may be too developer oriented.
You can find a list of tools specialized on requirements management here: http://www.softdevtools.com/search.php?query=requirements+management&action=results
We were always giving our clients access to the project backlog in our scrum tool. They could edit it there and we were always trying to get them to become Product Owners, usually with success. I see no reason why a client should not have access to the backlog the team is working off.