Highlighted
hanieeh Contributor.
Contributor.
41 views

Defect Sharing between Multiple Project

Hi,

In our company, we have ~40 projects and ~600 users. We have about 200 000 bugs and about 500000 test Plan altogether now, on the other hand the projects are closely integrated (banking systems). Most of project are related together so we want to share some defect.

I am not sure if in this case it is good to have all the applications in one ALM project or not. Close integration of the applications is in favor of the one big project, but risk of have one ALM project for all of our project and  complexity of variety test Plans and different entities need of different project are against.

 If we have multiple ALM project, how we can share some defects with multiple projects?

 We want to share some defect from one project to the others; For example: 

 First: in project P1, one user define defect D1 and assign to user U1.

 Then we want to: user U1 in P1, assign defect D1 to project P2 to user U2.

Is it possible? What is the solution? Thanks for any help

0 Likes
2 Replies
Honored Contributor.. machinedata Honored Contributor..
Honored Contributor..

Re: Defect Sharing between Multiple Project

You have a couple of options

First option is to use libraries for asset sharing ( eg. defects, tests, requirements) with ALM projects

Second option is to use the ALM synchronizer to sync defects between projects.

The second option might be your preferred route.  Much easier to maintain IMHO. 

Also, not really a good idea to have all your applications in one ALM project, for a lot of reasons. If projects need to share artifacts (and sync them) then libraries and baselines would be one solution to look into.

- MD

 

Knowledge Partner
Knowledge Partner

Re: Defect Sharing between Multiple Project

It is not so simple question in case you want to have it automatic.

If you need just manual synchronization then follow "machinedata" suggestions like share libraries or simple synchronization like ALM Synchronizer.

 

We had a third option in our company. I have created the online integration between the defect modul of all projects by workflow script.

Firstly I have set up the same custom field like "System", that contain all names of projects, in your case P1 and P2. Then user just edit the defect and select P2 in field System. After submiting of defect the workflow script create new defect in project P2 and lock the defect in P1. Now waiting for answer from project P2. After they will solve defect it is return to the project P1 (locked defect in P2 and unlocked in P1). Of course you need more custom fields in defect that will contain information about selected projects, which is active project, have the process for statuses how this integration works and so on. 

 

Also we have migrated from more projects to one big and I do not recommend to do that. Now we have more performance problem than before. Be tough and do not be defeated by managers that want one big project.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.