Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I'm currently using Jira Agile for managing my projects.Currently, I have 3 projects: A,B and C. Is there any way to create a Sprint with task from different projects. For example, this week should work on bug fixing so it might be expectable to have 2 bugs from project A, 3 bugs from project B and 2 from project C. How can I accomplish this?
I agree with mdoar, you simply need filters.
I'd create new Issue Type, let's say "Bug_fix_sprint" which is common for all projects, then open tickets with that type in each project, then I'd use Issue Type Filter to add them on dashboard. Or, maybe, I'd create a new dashboard for this sprint
The filter for your board needs to be changed to include the issues you want from all three projects
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I need to have more control on backlog....
Years ago, we have created a project using a SCRUM Process... Not all developers pay attenction to use correctly TFS... There are many problems I'd like to solve step by step...
First one... I would like to prevent to close a PBI until subtasks opened exist. Can be possible? I have looked for on google... I have looked for settings everywhere on tfs but it seems it is not possible... I remember that on Jira could be possible... is it possible that Microsoft haven't implemented this option?
Do you have any idea to avoid that subtask remain opened when parents are closed?
Thank you
There's no way to do that. The state of work items are totally independent of all other work items, including linked work items.
The best way to manage it at the moment that I've seen is to either:
Handle it via process: Be diligent about reviewing the sprint board and don't close user stories with open tasks
Write a work item query that shows you this information. Something like this will do the trick:
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Recently my company took Jira for Agile project management. As part of our process definition, we have a list of items that need to be covered in Sprint Planning (we used to use a checklist in trello for managing them). In Jira, how do we incorporate the checklist in Sprint Planning?
To handle checklists in JIRA Issues you can have a look at this plugin Checklist for JIRA.
For your use case I would prefer to handle Sprint Planning or any meetings in Confluence (if you can have it).
You can nicely link Confluence with JIRA Issues in both direction.
A couple of options spring to mind.
You could create a custom issue type called 'Sprint Planning' and add to it custom field checkboxes for each item on your checklist.
Alternatively you could just add in an issue and put the checklist in the 'Summary' field.
There may also be checklist plugins for JIRA (although I don't have any personal experience of them).
We also use Confluence page as a meeting agenda or checklist and the nice thing about Confluence page is that it is easy to reference issues from Jira and comes with a built-in checklist.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am currently working on a project where - while coding - there are some wishes about the layout (changing font color, changing the texts etc.)
What would be the best category in tfs?
bug, feature, issue or task?
I've read that: What are the differences among bugs, issues and tasks in TFS
But this did not help me on that question
To me, this would be either a Bug or a Feature.
It is a bug if it was supposed to be that way, and was not done.
It is a feature if it is a new idea/change.
After you create the bug/feature, you will add tasks to it as children. Those tasks should be the low level things needed for the overall feature to be done.
(By the way, if you are doing scrum, "features" are usually called Product Backlog Items. But both Bugs and Product Backlog Items go on the Product Backlog.)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
We're using TFS Work Items to manage our bugs and work items.
Would that be possible to use TFS for agile scrum project management? e.g. defining user stores, drawing burn down chart and cumulative chart, etc?
How?
Thanks
Absolutely yes.
Generate a new Team Project choosing the default process template (MSF for Agile Software Development 5.0) during the Wizard execution.
Now within this new Team Project a great deal of ready-baked reports is available, 'agile' work-item type User Story as well. Out-of-the-box sprint planning is also quite nicely delivered.
With a small time-investment for orientation, customizing & tailoring to your own needs should be possible.
A very comprehensive presentation by A.Bjork was really helpful for me.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I'm thinking of giving each part of the agile lifecycle its own project (TFS project, not csproj) as per Microsoft's agile template.
Is it possible to move items (like User Stories or Tasks) from one Project to another?
Does the organization of these projects have any bearing on or affect the actual software build (solutions, csproj, etc)?
What is the recommended organizational structure of Projects, etc for an agile project?
Are there any guides you can recommend for setting TFS up to work with the standard agile process?
Do not set up multiple TFS projects for the same team/product line. You can't move things from one to another and they won't be able to share a common parent source control so you would miss out on much of what source control has to offer. Do some research by reading the links on the other answers.
I have never heard such a strange idea.
You should have one team project for each endeavor. Basically, a team project is the intersection of a team with a project.