Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.
Hi all,
Up until now I haven't really been using the link to a planning activity for tickets, but now I would like to use this for a more important project.
Typically, I have several versions planned for a product, say V1 and V2, and depending on the priority of the tickets, I plan these either for V1 or V2. I then link the tickets to the corresponding activity "bug fixing V1" or "bug fixing V2" for example.
What I am missing however, is a link between the "estimated work" I enter for all my tickets, and the "planned work" on the linked activities.
I think it would be nice to have the "estimated work" added to the "planned work" for my "bug fixing" activities, that way I can immediately tell if I will be able to hold my V1 milestone with the current estimation of bug fixing work for V1.
Of course, I realize that tickets aren't really intended to be planned (unlike tasks), but since we have the option of linking a planning activity to a ticket, I think it would make sense to take into account the estimated work.
What do you think ?
Also, I'd be glad to hear from anyone who uses this feature in a different way, maybe there are alternatives 🙂
OK, I'm replying to myself... :whistle:
I've been thinking about why this was bothering me, and I've actually come to the conclusion that the reason is because I have recently "inherited" an ongoing project, and find myself doing things in an incorrect order.
Basically, I already have a bunch of known issues to deal with, but am only now trying to make a planning for our activities! :ohmy:
Good practice, of course, is to plan a certain amount of work for bug-fixing activities on version X, and then dip into that assigned work whenever bugs are being corrected (and therefore "real work" logged on tickets).
I guess what I'm saying is maybe you should not taking into account my request... 👿
(Anyway, sorry for thinking out loud!!)
Good practice, of course, is to plan a certain amount of work for bug-fixing activities on version X, and then dip into that assigned work whenever bugs are being corrected (and therefore "real work" logged on tickets).
You're completely right. It is exactly the way is was designed in Project'Or RIA.
I guess what I'm saying is maybe you should not taking into account my request...
I'm not so sure :huh:
There is realy somthing that may be missing : when you link tickets to a planning activity, there is no summary of estimated work and more important no sum for total left work on tickets; this is important (imo) to check that left work on activity is enought to fullfill left work on tickets...
I used to think about it but never recorded it 😉
It is done now : Ticket #1179 recorded !
Indeed, you understand my concern very well 🙂
Thanks!
I guess what I'm saying is maybe you should not taking into account my request...
I'm not so sure :huh:
There is realy somthing that may be missing : when you link tickets to a planning activity, there is no summary of estimated work and more important no sum for total left work on tickets; this is important (imo) to check that left work on activity is enought to fullfill left work on tickets...
I used to think about it but never recorded it 😉
It is done now : Ticket #1179 recorded !
Hurrah! Exactly the same issue for us using the system now. The process is:
Project comes in
We have a budget for the project
We can place all the development tickets to a development activity... But don't know the EXACT count of work with these tickets
As such it requires you to estimate every ticket, add up those estimations and then amend the planning activity... you add 2 more tickets and suddenly your planning activity doesn't accurately reflect actual work!
Fantastic if this makes it in.