Hi,
I think 'project' field in Ticket is wrong. It should be 'Product' not 'Project'!
In this case field 'original version' and 'target version' make sense because bugs are related to the product and version not to the project. Project can be optional but actually it covered by the 'target version' or 'origin' I believe
Regards,
Evgueni
Hi,
Ticket must be registered to a Project (at least to limit visibility).
And ticket is likable to Product through the Original version (it's not linked to the product, but the version of the product). This also introduce a link to project as Projects are linked to Versions.
In fact, Ticket existed much before Product was introduced and Product management is optional, so link to Project must be kept to avoid complete refactoring.
I disagree with that - defects are related to the product and the version. If we are talking about project then it is very difficult to define the problem in many cases:
- defect is found in current development project: Ok
- defect found in released version - to what project it should be raised?
Some people working different way: maintenance project may not yet be creaated, so issues are stored awaiting to be picked up when project will be created. Some of the issues may not go to that project let's say for different reasons and will be deferred for a while. Do not forget- the content of the project need to be approved based on time scale, budget, business cases, etc., so issues cannot be assigned to the project automatically
At least you should have a dummy project to attach tickets.
I never saw any ticket management, whatever the tool, where tickets are registered and no project is open for this.
Tickets not linked to a project will never be handled : no-one will ever take care of them.
Moreover, there is a technical need to attach tickets to a project. List of values in the ticket (Responsible, Planning Actvity, ...) are restricted to the project data.
This is unavoidable when dealing with a large number of Data.
I are currently ruinning some heavy volume tests (1000 projects, 500 resources, 10000 tickets, 10000 activities), and without this restriction, sytem would fall down.
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
Cookies settings
×
Functional Cookies
Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.
Session
Please login to see yours activities!
Other cookies
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.
Support us on Capterra
