View ProjeQtOr On
ProjeQtOr - Project Management Tool
Supportez nous sur Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - giving the customer the amount of spent effort - ProjeQtOr

Prochaines sessions de formation

Les prochaines formations et démonstrations sont ouvertes, inscrivez-vous rapidement !


Démonstration de ProjeQtOr

(gratuit, sur inscription)

Mardi 27 février (10h30-12h)

Mardi 19 mars (16h-17h30)

Mardi 23 avril (10h30-12h)

Jeudi 16 mai (16h-17h30)

Jeudi 13 juin (10h30-12h)


Planifiez avec ProjeQtOr

14 et 15 février (9h - 12h30)

3 et 4 avril (9h - 12h30)


Administrez avec ProjeQtOr

21 et 22 février (9h - 12h30)

10 et 11 avril (9h - 12h30)




giving the customer the amount of spent effort

29 Déc 2021 13:01 - 29 Déc 2021 13:17 #1 by al_rodin
Hi all!
Keeping in mind that the screen customization module exists, so probably using it to get what I'm going to ask should be possible, here first some:
Let's define Product assistance projects as time-capped (usually monthly assigned but yearly planned) contractualized pre-paid activities on which the customer opens some ticket, asking for time engagement on that in respect of some SLA. The resource will work on some related (linked) activities in the project but also he/she would possibly consume time directly on the ticket, without plan needing (let's say, for very small tasks).
Now, usually a customer buys this kind of assistance not in form of time but in form of, let's call them "coupons". Strictly speaking there's an equivalence between time and coupons (eg.: 1 coupon = 0.25hr or things like that), but this is not completely true because you can have different seniorities and differeent kinds of engagement on tickets (a 1st level helpdesk is not like a development task), so a "coupon translation table" (per customer, per resource , per ticket type and maybe per period/version, just for history) should exist, but this is not so important for the moment. 
Said that, here's the
how to show the total amount of planned coupons and consumed coupons to the customer for the ticket that he/she opened? No real effort in terms of time neither cost. Only coupons count in this case. I was imaging a pair of fields into tickets and simple tickets screens. This could be very useful because the customer periodically can ask for a report such as: number of coupons spent this month on tickets, trend of coupons consumption, and things like that.
Obviously, the best approach could be to have that coupon translation table, so in any moment the translation between effort and spent coupons is not only possible, but also automatic, as the result will vary depending on who's the customer, who's the resource, which kind of ticket type the resource is treating and lastly which version of the table is using (for history, as I said before).
If this table must be a built-in structure, so a perso occurrs in this case, then at least it would be nice to know if these two new additional fields can be filled syncing data captured from another software (through a cron job?). REST API calls are possible on the other side.
Best wishes!
Last edit: 29 Déc 2021 13:17 by al_rodin.

Please Connexion or Create an account to join the conversation.

29 Déc 2021 14:24 #2 by babynus
Best to do (IMO) : wait for V9.5.0
We are working on a sponsored evolution about this subject.

Administrator of ProjeQtOr web site

Please Connexion or Create an account to join the conversation.

29 Déc 2021 15:26 #3 by al_rodin
Hi babynus!
Great to know it! Thank you!
Best wishes!

Please Connexion or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.039 seconds

Paramétrages de cookies


Cookies fonctionnels

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.


Veuillez vous connecter pour voir vos activités!

Autres cookies

Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.