View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Support us on Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - Ticket - Project or Product? - ProjeQtOr
 
 

Ticket - Project or Product?

More
18 Sep 2012 10:05 #1 by ekolossov
Ticket currently related to the Project which making target version completely useless. I think it will be much better to have ticket related to the Product - in this case target version (which actually Project) will make sense. Can you please explain what the reasons to have ticket related to project?
Regards,
Evgueni

Please Log in or Create an account to join the conversation.

More
18 Sep 2012 10:12 #2 by babynus
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.

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

More
18 Sep 2012 10:20 #3 by ekolossov
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

Please Log in or Create an account to join the conversation.

More
18 Sep 2012 10:33 - 18 Sep 2012 10:33 #4 by babynus

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).

Babynus
Administrator of ProjeQtOr web site
Last edit: 18 Sep 2012 10:33 by babynus.

Please Log in or Create an account to join the conversation.

More
18 Sep 2012 10:41 #5 by ekolossov
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!!!

Please Log in or Create an account to join the conversation.

More
18 Sep 2012 10:46 #6 by babynus
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

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.036 seconds

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.