Forum

Ehancement when we ...
 
Notifications
Clear all

Ehancement when we create a ticket directly from an activity

2 Posts
2 Users
0 Reactions
3,230 Views
Damien
(@dnaton)
Posts: 248
Active Member
Topic starter
 
[#4057]

Hello,

On the "activityy" screen, I use sometimes the possibility to add a "link element" like ticket our meeting

On the screen to input the data for my ticket, I think it would be fine if the field "planning activity" would be completed automaticaly with the activity I come from.

Is it an interessant ehancement for you ?

Globally, it would be fine if this ehancement could be apply to all other creation (each time we create a link attachement directly from an activity, or meeting, or ticket)

In French to better comprehension (due to my poor English) 🙂

J'utilise la possibilité de créer un élément lié à partir d'une activité (comme par exemple un ticket, une réunion, un document,...)

Je trouver qu'il serait intéressant que dans l'élément que je crée (un ticket dans mon exemple ci-dessus), l'activité d'origine soit directement renseignée : après tout, on vient de cette activité, il me parait logique qu'elle soit renseignée par défaut, quitte à être modifiée par la personne si nécessaire.

On gagnerait en rapidité de saisie 🙂

De manière plus générale, ne pourrait-on pas généraliser ce fonctionnement à chaque fois que c'est possible quand on crée un élément lié ? Quand on connait d'où on vient pour créer cet élément lié, on le renseignerait alors par défaut ?

Thanks


Regards,
Damien
-----------------------------------------------
.
ProjeQtOr v12.1.0 - Apache v2.4.56 - MariaDB v10.4.28 - PHP v8.2.4
Plugins installed : PersonalizedTranslation 1.6 - ScreenCustomization 7.2

 
Posted : 01 Feb 2017 12H55
(@babynus)
Posts: 14952
Member Admin
 

It could be an improvement when creating items where current is "origin" for linked item.
But I'm afraid it may not in all cases.
For instance, you can create the link from "other side" (from Ticket) as link is bijective relationship.
And you can "link" ticket to activity for tickets that shoild not be included as part of planning activity work.
You can for instance link some ticket to some activity to specify that Ticket is a bug about this planned activity (perhaps an evolution). Without including work on Ticket on the activity.

Linking an Ticket to Activity and defining Planning Activity for Ticket has not the same meaning (except perhaps in your own case...).
But this kind of "shortcut" could be helpful in some case.
Ticket #2533 recorded, but not sure it will be done one day...


 
Posted : 01 Feb 2017 14H08
Share:

Scroll to Top