+176
Terminé

Add/link ticket to Project directly not only using project task

balucha il y a 9 ans mis à jour par glpi il y a 6 ans 12
We need to check how many tickets generate new project.

Solution

This was a feature in the plugin. I hope it returns.
Do you mean Projet plugin? This plugin has one problem, that I can`t add ticket from child entities.

Project is a good feature but in actual state is not useful as it could be.

Hi Balucha,


I don't really know the project plugin.

Could you be a little more precise about this supposed missing feature ?


Thanks in advance.

I don`t know the project plugin, too. I tested this plugin only for while by suggestion JBaily.


I mean Project feature in GLPI.

We want tickets generated by project link to this project. We need check how many tickets generate project(kind of tickets and other thing to evaluate project) Now we can`t do this simple way.

I can link ticket only this way -In selected project i must create project task and in project task I can add ticket.

It is too complicated way.

Good way is

1.in selected project add entry Ticket where I can add/link tickets(like adding items to projects or adding changes to project)

2.using massive action - mark tickets and link selected tickets to project using massive action

3.open ticket and link this ticket to project

As I wrote - Project is good feature but in actual state is not useful as it could be.

I believe it is for the sake of methodology.


From what I could understand of what you described, you want to be able to create a ticket and assign it to a task in the project, being that currently only the reverse is possible, project for ticket ..

Because I say it's a matter of methodology: Once you have the project registered, the tasks are just records of activities that need to be performed on demand, someone has already done the survey and planned what to do, the call would be to keep a history of the task ..

https://pt.wikipedia.org/wiki/Metodologia_de_projeto


You don`t understand me.

I want to assign ticket to project directly, not to task. Now it`s possible assign ticktet to project, but only using project task and this is a problem. It`s complicated and I can assign only opened tickets.


I give you example.

We have project named "Migration from MS Office to LibreOffice"

We have project team which tested migration, prepared methodology,.... and finaly created manuals for technicians

Technicians performed migration.

Now users works with LibreOffice and they founding bugs or things that not working.

What they will do? They will create tickets.

We need assign these ticket to project to see how many tickets generates this migration/this project and want to see types of these ticket. Project team gets these informations and adjust needed things in project,..... At the end we want to evaluate success of project.


Today I can`t do this simple way. I can`t assign ticket to project easily. I can`t assign resolved ticket to project,...

I can`t evaluate project. In this state the project is independent/autonomous feature without good relation to tickets.



Is GLPI currently able to make some success / impact returns?

Now I understand what you want to do, it seems interesting indeed!
But without having to measure this "ROI", it turns out to be just a tool of history, as I see it ..
My great use of GLPI is for the history of maintaining Equipment / Requests for repairs, which has no end, is just a history. , Where it is not possible to have expense metrics.

I have this idea to improve the item "inputs", but I think it will take a long time, because of the low relevance relevance they gave ..

GLPI is able but in limited degree (using link ticket function or using tag plugin) We was waiting for Project feature but we are disapointed. In actual state is not useful as it could be.

We need this feature to measure ROI. We need know history to do better in the future. We need to know impacts to evaluate projects.

Your use isn`t just history and you can have expense metrics. You need to measure and to record informations needed for expense metrics. From history you can learn to do thing better and find unknown/hidden informations.

We start using GLPI form same use -only evidence request for repair or help. But after some time we found that GLPI can help us to measure, to find hidden informations, to improve our work, to do our work easily,.....

We start using asset management and other features. Wwe start to learn how can GLPI help to us, but now we are in state that we found limitations of GLPI.

Look at my other requests. We need this features to work effectively.

http://glpi.userecho.com/topics/100-plan-ticket-not-only-ticket-tasks/

http://glpi.userecho.com/topics/129-regular-technical-inspection-on-items/

http://glpi.userecho.com/topics/513-option-to-assign-entities-to-groups-or-add-field-location-to-entities-and-search-tickets-by-this/


I have many other ideas to improve GLPI, this four ideas is most essential for us. I have some ideas from other people which contact me about installing and using GLPI. GLPI is great SW but not perfect.

I wrote long review (8 chapters),

https://www.linuxexpres.cz/software/glpi-kvalitny-open-source-helpdesk-a-sprava-it-zariadeni?highlightWords=glpi

I`d like to write a book about GLPI.

Hi,


I develop ability to link project with problems and tickets. It has been merged and will be available in next major version (not planned yet).


Regards

I would like a task-related call to be created after creating the task automatically. It would be great for our Project team.