Hi,
Every element is related to Project.
Project'Or RIA is a Project Management Tool, not just a bug tracker.

The interest is to link everything to a project.
Interest of version is major : have a look to Track Database, you'll see what I mean : one can easily point out what is planned on a version, when fixing or new fuctionality will be deployed...

Ticket is linked to product through the version.
Ease in linking is done while linking Project and Version.

Regards.

I guess that we have kind of different definition of project and product. From our point of view Projectorria is a product, version 2.5.1 - is a project

Projectorria is a product

True !

version 2.5.1 - is a project

No ! V2.5.1 is a ... Version of the product.

Developement of V2.5.1 is a project.
Maintenance of V2.4.x is another project.
All these projects could be included in a main Project, called Project'Or RIA (same as product).

This is exactly what I am talking about! You actually not using product at all because everything in your definition is the project. This is acceptable if you have one product. If you have many then you will have hierarchy:
Product A
---Project 1 = product A version 1
---Project 1.1 = product A version 1.1
Product B
---project 1 = product B version 1
---project 1.1 = product B version 1.1
So, any development or maintenance project related to the product!!!

Hi,
You're right.
But not only.
I often have :
Project 1 (Maintenance)
- Product A - V1 (maint)
- Product B - V1 (maint)
Project 2 (Dev)
- Product A - V2
Project 3 (Dev)
- Product B - V2
and possible (afterwards)
Project 4 (Dev)
- Product A - V3
- Product B - V3

All combinations are possible

No way!
This is completely wrong!

Hi Ekolossov,

basically you are right, maintenance is not a project.

But using a project management tool like Projectorria, you have to bite the bullet and say, Project is the term for a cluster of activites, actions, and so on.

I use Projectorria exact in the way as described by Babynus - and to be honest, nobody complains about that.

What is right or wrong is in the eye of the beholder. 😉
For me it's fine as it is.

Klaus

I think there is a potential to use Projectorria both ways which will make the tool much wider used. This can be achieved quite an easy actually by adding some necessary links, so option will be to link either project or product

hi,

Just to close this discussion, maybe Project'Or RIA does not fit the ISO definition of what is a project.
Just take it as a way to manage resources to work on "grouped" items.

The project entity is used to define access right management.
So removing the project level from tickets will remove all the access right management.
What is important, and defined throught project, is :
- "who can create new tickets" ?
- "who can see the tickets" ?
- "who can work on tickets" ?

Actually in this case I cannot see the point to have Product in projectorria - why you need it all?

You're right.
Product has no major interest, and has been introduced very late in the roadmap (on V1.7.0).
The only interest today is a descrptive part of tickets and activities, through the versions.

The main problem is - we cannot search tickets for product!!!
If you can just add Product (optional field) to the ticket it will cover that!

Hi,

Request registered as Ticket #785

Here is the description :
Product is optional.
If product is set, versions (origin and target) are limited to versions of product
If version is set, product is automatically set to product of version.
To think about : sub-product management
- searching for tickets on product criteria should also search for sub-products of the product.
- limit to versions should include version of sub-product

As a work around, you can :
- search for all versions of a product : will return all the tickets on the product
- you could define a top project called "Product A", on top of all projects about Product A. Then, selecting project "Product A" will select all tickets on product.

Notice that if "project 1" and "project 2" deal with "product A", if you have visibility only on "project 2", searching for "product A" tickets will never let you see tickets on "projet 1", even if they are on "product A"

Great!
Thank you very much!
This will do the job.
Do you have any time scale for implementation?
Regards,
Evgueni

No, request is not planned yet.

Please, Please - ASAP!!!