Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Is there a way to associate a single MS Project file with multiple TFS projects?
Here is the situation: I have two projects that are related and have dependencies on each other and I would like to have one MS Project file to coordinate the schedule. But, I do not see how I can associate (publish) to multiple TFS projects.
What I was trying to do is not possible. The correct way to handle the problem is to create a master schedule where multiple project files are linked to a master project file. Here is a video that describes this process: http://www.youtube.com/watch?v=DvJIZ7lCEDw
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 4 years ago.
Improve this question
I plan to use JIRA-Agile as used to:
EPIC->US->Task
Nevertheless, the JIRA is not only used by one project but rather by a couple of projects, which cooperate or even interfere in a few topics.
At the end I want to mark up which EPIC belongs to which project. I thought about to use labels or components, but for me it seems not very suitable. What is the best (may even standard) way representing this project structure above the EPIC level ?
Features I need:
Epic can belong to more than one Project
Epic can be shifted between projects
Projects existing on different levels (one Project can even combine 2 smaller one)
"nearly" automatic reporting export is possible
Project structure can be "read" from the Jira
Are you asking about project management and analysis in jira.?
if so then you can see if the Jira Portfolio management app works for you
https://www.atlassian.com/blog/jira-service-desk/portfolio-for-jira-2-0-is-here
I am not sure how Epic will help in your case -- lets hear more answers here.
Well i am not sure if a jql will make it happen, but https://softwareplant.com/jira-aggregate-multiple-sprints-single-screen/ could help you.!
it has an option to view the board based on Epic, userstory also.!
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
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I need to find an easy way to maintain a set of different iOS apps but that they will be very similar one to another. Too similar actually, the differences will be just regarding the content.
Following the typical way of releasing/updating an app, it would imply:
Create a "core project" of the app with all the functionality and UI.
Create n projects that reuses the core project. Every project would just provide a DB with different content.
Having to release/update every single project/app to the AppStore
This would be too time consuming. Is there a tool or a methodology that can help us speed up the process and help the maintenance?
The built in process for this is to create multiple targets in a single project. Each target will have its own info plist, etc.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 2 years ago.
Improve this question
I am liking JIRA a lot, but we need a CLIENT/PROJECT/ISSUE Schema. Not Just Project and issue. It seems that Projects in JIRA are actually Clients. If you have many clients each with its own projects and issues it seems silly that you cant manage clients. It does so many other things so well, it seems strange.
Some companies indeed use JIRA Project as clients, and use JIRA Components (which are parts of a project) as the projects.
Note that permissions, issue types and other configuration "schemes" in JIRA are configured per-project, not per-component. That means that with this schema you will be able to set up permissions for all issues belonging to a specific client.
Versions are also set per JIRA Project, i.e. per client in this case, which also might not be good.
JIRA also has Project Categories. If you have a small number of clients, you might do better with assigning a client to a project category, and then project will be JIRA project.
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.